While Postgresql does use the Apache model, there is middleware available (google 'pgpool' for an example) that amongst other things will queue requests so they can be serviced by a limited number of children. Of course this only matters if there are an awful lot of simultaneous queries (without the corresponding amount of server RAM).
However; your claim about threads per CPU is oversimplified, and especially wrong with a DB server where processes will most likely be IO bound. With 1 core, for example, there is nothing wrong with having 5 processes parsing and planning a query for a few microseconds, while the 6th is monopolising IO actually retrieving query results. Or the reverse - having 1 CPU-bound process occasionally being interrupted to service 5 IO bound processes, which would negligibly impact the CPU-bound query, while hugely improving latency on the IO bound queries.
But whatever the cause, the point is that something like that should not pass without comment; that it has done indicates to me that the reviewer may not be particularly familiar with the subject.
The only other thing to be gleaned from the graphs is that running at 96kHz is pointless because the supposedly better cards' performance FUCKING SUCKS past 20kHz.
The justices in London outlined a litany of concerns in their June 20 decision, noting offenders don't have to be mentally ill to be committed; their offenses don't have to be recent; and in some cases, they don't even have to have been convicted of a crime.
As of April 1, 641 people were in Minnesota's program...some who say it holds people indefinitely after their prison sentences. One 64-year-old man received a provisional discharge earlier this year...Only one other person was ever released from the program, and was soon taken back into custody on a violation.
Sure it won't create an instance of Array, but if you're using an Array to also be an associative array then really I think JSON is the least of your worries.
But it does move! -- Galileo Galilei