Re: [PERFORM] Opteron vs. Xeon "benchmark"

2006-09-23 Thread Dave Cramer
On 23-Sep-06, at 9:49 AM, Guido Neitzer wrote: On 9/23/06, Dave Cramer <[EMAIL PROTECTED]> wrote: 1) The database fits entirely in memory, so this is really only testing CPU, not I/O which should be taken into account IMO I don't think this really is a reason that MySQL broke down on ten or

Re: [PERFORM] Update on high concurrency OLTP application and Postgres

2006-09-23 Thread Cosimo Streppone
Christian Storm wrote: At the moment, my rule of thumb is to check out the ANALYZE VERBOSE messages to see if all table pages are being scanned. INFO: "mytable": scanned xxx of yyy pages, containing ... If xxx = yyy, then I keep statistics at the current level. When xxx is way less than yyy,

Re: [PERFORM] Opteron vs. Xeon "benchmark"

2006-09-23 Thread Guido Neitzer
On 9/23/06, Dave Cramer <[EMAIL PROTECTED]> wrote: 1) The database fits entirely in memory, so this is really only testing CPU, not I/O which should be taken into account IMO I don't think this really is a reason that MySQL broke down on ten or more concurrent connections. The RAM might be, bu

Re: [PERFORM] Opteron vs. Xeon "benchmark"

2006-09-23 Thread Dave Cramer
On 23-Sep-06, at 9:00 AM, Guido Neitzer wrote: I find the benchmark much more interesting in comparing PostgreSQL to MySQL than Intel to AMD. It might be as biased as other "benchmarks" but it shows clearly something that a lot of PostgreSQL user always thought: MySQL gives up on concurrency ..

Re: [PERFORM] Opteron vs. Xeon "benchmark"

2006-09-23 Thread Guido Neitzer
I find the benchmark much more interesting in comparing PostgreSQL to MySQL than Intel to AMD. It might be as biased as other "benchmarks" but it shows clearly something that a lot of PostgreSQL user always thought: MySQL gives up on concurrency ... it just doesn't scale well. cug On 9/23/06, [

Re: [PERFORM] Confusion and Questions about blocks read

2006-09-23 Thread Markus Schaber
Hi, Tom, Tom Lane wrote: > "Alex Turner" <[EMAIL PROTECTED]> writes: >> Home come the query statistics showed that 229066 blocks where read given >> that all the blocks in all the tables put together only total 122968? > > You forgot to count the indexes. Also, the use of indexscans in the > mer

Re: [PERFORM] recommended benchmarks

2006-09-23 Thread Denis Lussier
If the real world applications you'll be running on the box are Java (or use lots of prepared statements and no stored procedures)... try BenchmarkSQL from pgFoundry. Its extremely easy to setup and use. Like the DBT2, it's an oltp benchmark that is similar to the tpc-c. --Denis Lussier http:/