-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2014-09-16 01:29, Claudio Freire wrote:
On Mon, Sep 15, 2014 at 8:25 PM, Carlos E. R.
So it is obvious! We simply run the cp to null thing ahead of the query on the script, and done.
Yes, it's a nice band-aid if the system has enough memory.
Not so much if it doesn't.
True. It is a hack, or band-aid, as you say. The real problem is how the database engine is coded: it is made, apparently, to minimize ram, doing non-sequential and non-cached disk reads. When I wrote a small database "engine" long ago, I did the same thing: it worked on disk, small memory foot print. It was how we were taught to do those things at the year... but it is 2014 now: If memory is available, use it to your advantage, somehow. No, I do not know the proper "somehow". - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlQXeZIACgkQtTMYHG2NR9UrogCdFbi9hxApFlyk3275mc6lgKrS RoAAoJPTulLKtUo++fxdAfShiCh830uN =mCJz -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org