09.02.2012 20:58, Leyne, Sean wrote:
>
> What Thomas is looking to define is a setup where an RAM would be the first
> device for the temp results (to enable much faster processing -- RAM disk has
> 100x IO of even an SSD!!), with any excess falling to an SSD or HDD. The
> approach/setup is per
>> What Thomas is looking to define is a setup where an RAM would be the first
>> device for the temp results (to enable much faster processing -- RAM disk
>> has 100x IO of even an SSD!!), with any excess falling to an SSD or HDD.
>> The approach/setup is perfectly reasonable -- it tries to pl
Dmitry,
> > Splitting temp destinations into e.g. RAM disk and if this is
> > exhausted to regular disk is getting more and more popular, but due to
> > CORE-2422,
>
> So far nobody has proved that this approach is better than adjusting
> TempCacheLimit.
I don't see the TempCacheLimit as being r
09.02.2012 17:58, Thomas Steinmaurer wrote:
>
> Splitting temp destinations into e.g. RAM disk and if this is exhausted
> to regular disk is getting more and more popular, but due to CORE-2422,
So far nobody has proved that this approach is better than adjusting
TempCacheLimit.
> this doesn't se
Hi,
a related tracker ref is: http://tracker.firebirdsql.org/browse/CORE-3757
Nick Upson
On 9 February 2012 13:58, Thomas Steinmaurer wrote:
> Hello,
>
> according to various bug fix lists/documents, it seems CORE-2422 is
> present in 2.1.x, I also haven't found an evidence in the 2.1.5 snap
Hello,
according to various bug fix lists/documents, it seems CORE-2422 is
present in 2.1.x, I also haven't found an evidence in the 2.1.5 snapshot
change log, that it is fixed in 2.1.5.
Splitting temp destinations into e.g. RAM disk and if this is exhausted
to regular disk is getting more and
