I sometimes experience that updating smaller sets is more efficient than
doing all at once in one transaction (talking about 1+)
Always make sure the update references can make use of indices
On Fri, Aug 9, 2013 at 5:44 PM, Kevin Grittner wrote:
> Robert DiFalco wrote:
>
> > In my system
ever tried symlinking?
On Dec 3, 2011 5:09 AM, "Tory M Blue" wrote:
> So we are making progress on our performance issues, we are splitting
> the data, changing the index value etc. So far having some success,
> but we also want to test out some of the options and changes in the 9
> branch, but
Have you also created your partitions with a reasonably new fdisk (or
equivalent) with -c -u as options?
Your partitions should be starting somewhere at 2048 i guess (let the
sw figure that out). The fast degradation of the one disk might
indicate bad partitioning? (maybe recheck with a grml.iso o
Use a replicated setup?
On Nov 8, 2010 4:21 PM, "Lello, Nick" wrote:
How about either:-
a) Size the pool so all your data fits into it.
b) Use a RAM-based filesystem (ie: a memory disk or SSD) for the
data storage [memory disk will be faster] with a Smaller pool
- Your seed data should be
