On 07.01.2013 20:51, Pavel Bortnovskiy wrote:
Hello:
This is more of a general question. Our application uses Derby in the
in-memory mode only.
When the application is configured to use complex queries, such
configuration causes CPU utilization (on the Linux server) to go as
high as 300% or even higher. Using simpler queries don't seem to lead
to such high utilization. Is there any way to control or lower CPU
utilization by Derby?
Hi Pavel,
I don't believe there is such a mechanism in place, at least not
specifically for the in-memory back end.
Since this is in-memory, the latency associated with page operations is
very low. Do you know if Derby is using the CPU for something useful
(i.e. processing queries effectively), or is the CPU spent on wasteful
activities?
One potential wasteful activity is moving data back and forth from the
page cache (page cache too small?).
Is this a highly concurrent scenario?
Regards,
--
Kristian
Thank you,
Pavel.
Jefferies archives and monitors outgoing and incoming
e-mail. The contents of this email, including any
attachments, are confidential to the ordinary user of the
email address to which it was addressed. If you are not
the addressee of this email you may not copy, forward,
disclose or otherwise use it or any part of it in any form
whatsoever. This email may be produced at the request of
regulators or in connection with civil litigation.
Jefferies accepts no liability for any errors or omissions
arising as a result of transmission. Use by other than
intended recipients is prohibited. In the United Kingdom,
Jefferies operates as Jefferies International Limited;
registered in England: no. 1978621; registered office:
Vintners Place, 68 Upper Thames Street, London EC4V 3BJ.
Jefferies International Limited is authorised and
regulated by the Financial Services Authority.
