Posted by Rob Pungello on March 15, 2016 at 13:48:16:
We've recently moved an XAP application to Rackspace, where we now have four processor cores to play with instead of only two on the server we previously used (which was located in our office).
Comet does seem to be able to take advantage of multiple cores, because running multiple lookups simultaneously does increase the load on all the cores, but we only seem to be able to hit 30-40% CPU utilization regardless of how many simultaneous lookups we run. As lookups are added, the per thread utilization drops.
When we only had two cores on the Rackspace server, we were able to hit 70-80%.
The disks in use by the server are SSDs, so it's unlikely there's an I/O bottleneck being hit.
I'm wondering if there's a central part of Comet (maybe the DB/file services) that are bound to a single thread, which means once that threads maxes out a core, other threads relying on Comet Files cannot run at full speed.
Each file can be a maximum of 1MB in length Uploaded files will be purged from the server on a regular basis.