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. Dmitry ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_nov Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
