On 3/23/19 7:45 PM, Fabien COELHO wrote: > >>>> What is the point of that, and if there is a point, why is it nowhere >>>> mentioned in pgbench.sgml? >> >> The attached patch simplifies the code by erroring on cache overflow, >> instead of the LRU replacement strategy and unhelpful final report. >> The above lines are removed. > Eh? Do I understand correctly that pgbench might start failing after some random amount of time, instead of reporting the overflow at the end? I'm not sure that's really an improvement ... Why is the cache fixed-size at all? regards -- Tomas Vondra http://www.2ndQuadrant.com PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
- Re: CPU costs of random_zipfian in pgbench Georgios Kokolatos
- Re: CPU costs of random_zipfian in pgbench Fabien COELHO
- Re: CPU costs of random_zipfian in pgbench Georgios Kokolatos
- Re: CPU costs of random_zipfian in pgbench Tom Lane
- Re: CPU costs of random_zipfian in pgbench Fabien COELHO
- Re: CPU costs of random_zipfian in pgb... Fabien COELHO
- Re: CPU costs of random_zipfian i... Fabien COELHO
- Re: CPU costs of random_zipfi... Tomas Vondra
- Re: CPU costs of random_z... Fabien COELHO
- Re: CPU costs of random_zipfian in pgb... Tomas Vondra
- Re: CPU costs of random_zipfian i... Fabien COELHO
- Re: CPU costs of random_zipfi... Fabien COELHO
- Re: CPU costs of random_z... Tom Lane
- Re: CPU costs of random_z... Fabien COELHO
- Re: CPU costs of random_z... Tom Lane
- Re: CPU costs of random_z... Alvaro Herrera
- Re: CPU costs of random_z... Tom Lane
- Re: CPU costs of random_z... Fabien COELHO