On 12/19/2010 7:57 PM, James Cloos wrote:
"RA" == Royce Ausburn writes:
RA> I notice that when restoring a DB on a laptop with an SDD,
RA> typically postgres is maxing out a CPU - even during a COPY.
The time the CPUs spend waiting on system RAM shows up as CPU
time, not as Wait time. It co
> "RA" == Royce Ausburn writes:
RA> I notice that when restoring a DB on a laptop with an SDD,
RA> typically postgres is maxing out a CPU - even during a COPY.
The time the CPUs spend waiting on system RAM shows up as CPU
time, not as Wait time. It could be just that the SSD is fast
enough
On Dec 17, 2010, at 8:46 PM, Robert Haas wrote:
> 2010/12/6 pasman pasmański :
>> hello.
>>
>> i tested how are distributed values xmin,xmax on pages.
>> in my tables . typically there are no more than 80 records
>> on pages.
>>
>> maybe its possible to compress xmin & xmax values to
>> 1 byte/pe
Thanks for ur suggestion, already I have gone through that url, with that
help I was able to make my configuration to work for 5K queries/second.
The parameters I changed was shared_buffer, work_mem, maintenance_work_mem
and effective_cache.
Still I was not able to reach my target.
Can u kindly
> If you strictly have an OLTP workload, with lots of simultaneous
> connections issuing queries across small chunks of data, then
> PostgreSQL would be a good match for SQL server.
This matches my observations. In fact, PostgreSQL's MVCC seems to work
heavily in my favor in OLTP workloads.
> On
My requirement is more than 15 thousand queries will run,
It will be 5000 updates and 5000 insert and rest will be select.
Each query will be executed in each psql client, (let say for 15000 queries
15000 thousand psql connections will be made).
Since the connections are more for me the performa
