Hi, Any ideas why most calls to bgapi take 20ms (on avg) on my idle quad core FC10 box doing a single transaction at a time ? Can do 300 call per second on that box using SIPP but when a single process tries to control my FS instance using a single ESL socket than 95% of the bgapi calls return job-id in 20ms. The rest takes under a millisecond as it should. Is it possible that thread creation takes 20ms or that the job thread itself gets it's CPU timeslice before the job-id gets sent out (hardly possible with 4 CPU threads) ? I have not done any benchmarking yet to see where the real delay is - but it is visible on the loopback interface and limits the performance of my inbound socket app. a fast one: bgapi uuid_displace fca427df-a8b0-4aff-8041-e328691dea3d start tone_stream://v=-10;%(150,100,400,450);loops=2 ### T +0.001165 127.0.0.1:18022 -> 127.0.0.1:44944 [AP] Content-Type: command/reply Reply-Text: +OK Job-UUID: 73f5ac5f-f3b5-44f0-a839-1b5c785b3ae7 Job-UUID: 73f5ac5f-f3b5-44f0-a839-1b5c785b3ae7 a 20ms delay for similar calls bgapi uuid_displace 380e9f71-f6f2-3b94-3ae0-bc6437bed887 start tone_stream://v=-10;%(150,100,400,450);loops=2 ### T +0.020224 127.0.0.1:18022 -> 127.0.0.1:44944 [AP] Content-Type: command/reply Reply-Text: +OK Job-UUID: a7bc6bc9-b7ed-4c8b-a55d-61a48427ceb9 Job-UUID: a7bc6bc9-b7ed-4c8b-a55d-61a48427ceb9 Pawel,