On 05/04/2012 09:57 AM, Albe Laurenz wrote:
> Martin Grotzke wrote:
>>> You could try different kernel I/O elevators and see if that
>>> improves something.
>>>
>>> I have made good experiences with elevator=deadline and
>>> elevator=noop.
>
>> Ok, great info.
>>
>> I'm not sure at which device
Martin Grotzke wrote:
>> You could try different kernel I/O elevators and see if that improves
>> something.
>>
>> I have made good experiences with elevator=deadline and
elevator=noop.
> Ok, great info.
>
> I'm not sure at which device to look honestly to check the current
> configuration.
>
>
Hi Laurenz,
On 05/03/2012 09:26 AM, Albe Laurenz wrote:
> Martin Grotzke wrote:
>> we want to see if we can gain better performance with our postgresql
>> database. In the last year the amount of data growed from ~25G to now
>> ~140G and we're currently developing a new feature that needs to get
>
Martin Grotzke wrote:
> we want to see if we can gain better performance with our postgresql
> database. In the last year the amount of data growed from ~25G to now
> ~140G and we're currently developing a new feature that needs to get
> data faster from the database. The system is both read and wr
Hi,
On 2 Květen 2012, 15:19, Martin Grotzke wrote:
> Hi,
>
> we want to see if we can gain better performance with our postgresql
> database. In the last year the amount of data growed from ~25G to now
> ~140G and we're currently developing a new feature that needs to get
> data faster from the da
Hi,
we want to see if we can gain better performance with our postgresql
database. In the last year the amount of data growed from ~25G to now
~140G and we're currently developing a new feature that needs to get
data faster from the database. The system is both read and write heavy.
At first I wa
