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. First half (comment limits:)

  0:36:428 UART-Request 'ble.send'
  0:36:429 Setting BLE parameters err_code:0
  0:36:429 PA LNA setting: 0
  0:36:429 Prefered params(st:0): min:30 max:100 latency:0 timeout:400
  0:36:430 UART-Init bucket 1 chunks, 5 chars in queue. 0 in buffer 
  0:36:966 Connection for device 0 status: 0  (state : 0)
  0:37:968 Connection Callback (6 Tx buffers available)
  0:39:095 Terminated SD for handle 0.
  0:39:095 Send command 'info;' for connection 0
  0:39:595 BLE-data (off=0, len=22) bodyLen:119
  0:39:595 FRAME sNode:2 seq:0 dNode:0 fType:1 bLen:119 bType:0
  0:39:595 FRAME body: '?=========== ?'
  0:39:595 Incomplete packet.Fragment: 22 != (119 + 9)
  0:39:596 Wait for bucket (off=22) st=0x0
  0:39:845 BLE-data (off=22, len=22) bodyLen:119
  0:39:845 Incomplete packet.Fragment: 44 != (119 + 9)