frees divide - Search results in mailing lists
Mailing lists >> pgsql-performance >> Thread
2024-12-10 08:32:44 | Re: PostgreSQL and a Catch-22 Issue related to dead rows (Lars Aksel Opsahl)
free lunch here. Maybe there's some other compromise between amount-of-state-exposed versus dead-row-discoverability, but finding a better way would take a great deal of creative effort and testing. regards
Mailing lists >> pgsql-performance >> Thread
2020-02-26 16:17:21 | much slower query in production (Guillaume Cottenceau)
free buff cache si so bi bo in cs us sy id wa 0 0 480712
Mailing lists >> pgsql-performance >> Thread
2019-02-20 23:32:49 | neither CPU nor IO bound, but throttled performance (Gunther)
free, 0 used. 2223720 avail Mem PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 7678 postgres 20 0 1235072 509744 506356 R 8.7 12.6 1:14.82 postgres: auser integrator
Mailing lists >> pgsql-performance >> Thread
2018-05-21 17:12:06 | Re: Help me in reducing the CPU cost for the high cost query below,as (Abbas)
divide the fractional part ( effort_hours - floor(effort_hours) ) by .6 to get what you want. For example, let's say effort_hours = 1.15; then floor(1.15) is 1; so: floor(1.15) + ( (1.15 - floor
Mailing lists >> pgsql-performance >> Thread
2017-04-13 22:30:54 | [PERFORM] Postgresql, and ODBC handles (Reza Taheri)
divide these threads into 5 processes, performance nearly doubles. So, the problem is not in the database backend. Each thread has its own database connection and its own statement handle. Looking more closely
Mailing lists >> pgsql-performance >> Thread >> Search in thread (2)
2009-06-29 18:21:35 | Re: Utilizing multiple cores in a function call. (Merlin Moncure)
divide up the work logically into separate pools and to attack the work with multiple function calls. This is probably what the database would do for you if it had 'in-query multi threading', only
Mailing lists >> pgsql-performance >> Thread
2009-03-18 09:53:02 | parallelizing slow queries for multiple cores (PostgreSQL + Gearman) (henk de wit)
divided the workload in 4 equal portions: day 1 to 15, 16 to 30, 31 to 45 and 46 till 60. The speed up I measured was only a little less then a factor
Mailing lists >> pgsql-performance >> Thread
2007-12-27 09:50:18 | Re: With 4 disks should I go for RAID 5 or RAID 10 (Bill Moran)
divides requests up among multiple drives. I'm unclear as to how you reached a conclusion opposite of what the man page says -- did you test and find it not to work? -- Bill Moran Collaborative
Mailing lists >> pgsql-performance >> Thread
2007-09-06 15:18:11 | Re: Hardware spec] (Jean-David Beyer)
dividing the stuff up with the indices separate from the associated data to reduce seeking. $ vmstat 30 procs -----------memory---------- ---swap-- -----io---- --system-- - -----cpu------ r b swpd free
Mailing lists >> pgsql-performance >> Thread
2007-04-12 12:34:08 | Re: Slow Postgresql server (Jeff Frost)
free' command and take the cache number and divide by 8 to get a reasonable
Mailing lists >> pgsql-performance >> Thread
2006-12-29 13:15:49 | Postgresql Configutation and overflow (Fabricio Peñuelas)
divided the load with another server for better performance, and now reach 500 connections, but yet is overflow. My question is about how much memory should i configure in shared_buffers and effective_cache_size
Mailing lists >> pgsql-performance >> Thread >> Search in thread (2)
2006-12-28 21:58:32 | Postgresql Configutation and overflow (fabrix peñuelas)
divided the load with another server for better performance, and now reach 500 connections, but yet is overflow. My question is about how much memory should i configure in shared_buffers and effective_cache_size
Mailing lists >> pgsql-performance >> Thread
2006-04-25 15:14:58 | Large (8M) cache vs. dual-core CPUs (Bill Moran)
divided over which is likely to be better, and I have been unable to discover a method for estimating how much of the 2M cache on our existing systems is being used. Does anyone
Mailing lists >> pgsql-performance >> Thread
2005-01-06 12:15:43 | Re: Low Performance for big hospital server .. (Dawid Kuroczko)
Divide the update, if possible. This way query uses less memory and you may call VACUUM inbetween updates. To do this, first SELECT INTO TEMPORARY table the list of rows to update (their
Mailing lists >> pgsql-performance >> Thread
2004-10-07 18:11:26 | Re: Data warehousing requirements (Gabriele Bartolini)
divide a table into 2 tables (like if I cut them vertically, right?) having the same key. If I had 2 extra columns, that could be the case, couldn't it? In this case