> Fra: Dmitry Yemanov [mailto:firebi...@yandex.ru] > > 12.11.2012 16:52, vince.dug...@virginactive.co.za wrote: > > > > When running under load (150+ busy connections) SuperClassic clearly > > uses only one NUMA node (threads are spread across 16 cores), while > > Classic is spread evenly across all 64 cores. > > Weird, I'd expect them behaving the same way. Perhaps this is somewhat OS > related. > > > How is this going to run in V3? Will we see full use of all cores on > > all processors, or will the behaviour be as in SuperClassic. > > Supposedly, it would be the same as in SuperClassic. But so far it doesn't > look > like a Firebird issue, it belongs elsewhere. > > > Is this a machine architectural issue? i.e. the NUMA node architecture > > makes it a little more difficult for one NUMA node to access the > > memory 'allocated' to another NUMA node? > > A little more difficult - true, but it should mean "a little slower", not > preventing that completely.
I could put a screen dump here of the Windows 2008R2/63 task manager with AMD Opteron 6274, 2x16 core running FB2.5.1 SC/32 bit (due to some 32 bit UDF). I don't know if you are interested at a gaze. We see exactly the same kind of usage, 8 cores are in use and 24 are more or less doing nothing. However, the cores in use are not maxed out - so it COULD be something with power management that the OS doesn't want to activate more CPU's than necessary. I can't tell about that for sure. Best regards Poul ------------------------------------------------------------------------------ Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
