Re: gprof SELECT COUNT(*) results
- From: Qingqing Zhou <zhouqq(at)cs(dot)toronto(dot)edu>
- To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- Cc: Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org
- Subject: Re: gprof SELECT COUNT(*) results
- Date: Fri, 25 Nov 2005 12:57:20 -0500 (EST)
- Message-id: <Pine(dot)LNX(dot)4(dot)58(dot)0511251247030(dot)26007(at)eon(dot)cs>
On Fri, 25 Nov 2005, Tom Lane wrote:
>
> Is that "modern machine" a Xeon by any chance?
>
$#cat /proc/cpuinfo | grep "model name"
model name : Intel(R) Pentium(R) 4 CPU 2.40GHz
I can find a 4way Xeon (but it is shared by many users):
/h/164/zhouqq#cat /proc/cpuinfo |grep "model name"
model name : Intel(R) Xeon(TM) CPU 2.40GHz
model name : Intel(R) Xeon(TM) CPU 2.40GHz
model name : Intel(R) Xeon(TM) CPU 2.40GHz
model name : Intel(R) Xeon(TM) CPU 2.40GHz
$/pgsql/src/backend/storage/lmgr#./a.out
Spinlock pair(2648542) duration: 161.785 ms
$/pgsql/src/backend/storage/lmgr#./a.out
Spinlock pair(2648542) duration: 160.661 ms
$/pgsql/src/backend/storage/lmgr#./a.out
Spinlock pair(2648542) duration: 155.505 ms
>
> it now occurs to me that you could still cherry-pick non-corrupt tuples
> with TID-scan queries, so this objection shouldn't be considered fatal.
>
It is great that it is not that difficult to do it! What's more, the
parallel scan will be easier to implement based on page level scan
operators.
Regards,
Qingqing
Home |
Main Index |
Thread Index