2016-12-14 16:31 GMT-03:00 Ramon Leon <ramon.l...@allresnet.com>: > On 12/14/2016 10:27 AM, Esteban A. Maringolo wrote: >> >> Memory is cheap, and the only limit now is CPU, the current Pharo >> image has an idle CPU consumption ~5%, so you can't have many >> concurrent images running in the same machine. > > > Sure you can, a multi-core server isn't going to get maxed out by idle CPU > consumption as each image will only do that on a single core; you can also > reduce consumption on headless images by suspending the UI process which > isn't needed getting you down to perhaps 2-3%.
Can you extend on suspending the UI process? I never did that. >> whilst 10 idle Pharo images will consume 50%. > Only on a single CPU machine which isn't what you're going to have on a > server. Running two images per core on a 12 core virtual server and you'll > be sitting more like 5-6% idle which is totally fine. Spread that across 10 > or 15 virtual servers and you can handle 1000 concurrent users just fine. Won't the idle use add up? In my case I served up to 20 concurrent users (out of ~100 total) with only 5 images. Plus another two images for the REST API. In a dual core server. Regards. Esteban A. Maringolo
