Subject Re: [firebird-support] Re: UK based Firebird on Linux expert
Author Steve Wiser
You should run top as you are running the long queries or gbaks and see if
the CPU is maxed out, the memory is swapping, or the CPU is in constant IO
wait. That should help narrow down if there is a resource problem.

-steve

--
Steve Wiser
President
Specialized Business Software
6325 Cochran Road, Unit 1
Solon, OH 44139

www.specializedbusinesssoftware.com
www.docunym.com
(440) 542-9145 - fax (440) 542-9143
Toll Free: (866) 328-4936




On Fri, Nov 25, 2011 at 6:32 AM, Milan Babuskov <milanb@...> wrote:

> **
>
>
> grip_2ls wrote:
> > xfs ok for Firebird?
>
> It depends on the kernel version, there were some nasty bugs in kernels
> 2.6.0 up to 2.6.9 IIRC that can corrupt your database if you use forced
> writes (sounds counter intuitive, I know). For kernels 2.6.10 and above
> you should be fine.
>
> But it's still slower than ext3/4 and reiserfs when forced writes are
> on. I did some bencmarks about 2 years ago and it was about 25% slower
> or random insert/update/delete stuff. Of course, each benchmark can be
> tweaked, I just tried typical load by users of my application.
>
> --
> Milan Babuskov
>
> ==================================
> The easiest way to import XML, CSV
> and textual files into Firebird:
> http://www.guacosoft.com/xmlwizard
> ==================================
>
>
>
>
> This message and any files transmitted with it may contain information
> that is privileged, confidential, and exempt from disclosure under
> applicable law. They are intended solely for the use of the intended
> recipient. If you are not the intended recipient, distributing, copying,
> disclosing, or reliance on the contents of this communication is strictly
> prohibited. If this has reached you in error, kindly destroy this message
> and notify the sender immediately. Thank you for your assistance.
>
> We attempt to sweep harmful content (e.g. viruses) from e-mail and
> attachments, however we cannot guarantee their safety and can accept no
> liability for any resulting damage. The recipient is responsible to verify
> the safety of this message and any attachments before accepting them.
>


[Non-text portions of this message have been removed]