Why 250 ms interval between subsequent reads?

[HeS]

I observe strange behavior while reading value for long characteristics.

I have characteristic 100 bytes long (read only). In GATT client I must read value with subsequent reads (sd_ble_gattc_read with proper offsets). Everything works fine with one exception. Subsequent packets are received at intervals of 250 ms. Why? Where is this "magic interval" set? With my characteristic 100 byte long I need spend 1 second to get full value (and keep connection!).

[HeS]

Receiver log second half:

  0:39:845 Wait for bucket (off=44) st=0x0
  0:40:095 BLE-data (off=44, len=22) bodyLen:119
  0:40:095 Incomplete packet.Fragment: 66 != (119 + 9)
  0:40:095 Wait for bucket (off=66) st=0x0
  0:40:345 BLE-data (off=66, len=22) bodyLen:119
  0:40:345 Incomplete packet.Fragment: 88 != (119 + 9)
  0:40:345 Wait for bucket (off=88) st=0x0
  0:40:595 BLE-data (off=88, len=22) bodyLen:119
  0:40:595 Incomplete packet.Fragment: 110 != (119 + 9)
  0:40:595 Wait for bucket (off=110) st=0x0
  0:40:845 BLE-data (off=110, len=18) bodyLen:119
  0:40:845 BLE-packet completed (ftype:1) btype:0, len:119
  0:41:095 Disconnected for connection 0
  0:49:414 UART-Request 'log'