| |||||||||||||
How 3.6 nearly broke PostgreSQLHow 3.6 nearly broke PostgreSQLPosted Oct 12, 2012 1:27 UTC (Fri) by bjmaz (guest, #87170)Parent article: How 3.6 nearly broke PostgreSQL
Seems to me a solution to this problem could be to dedicate a core to scheduling. This, of course, would assume a many-core, homogenous system. The scheduler could then keep track of free resources/running processes.
(Log in to post comments)
|
|||||||||||||