Re: ODP: [firebird-support] Re: Objects cached in FB memory

2019-06-21 Thread m_brahi...@yahoo.fr [firebird-support]
Because I need to know if compiled views are cached in memory a the sp

ODP: [firebird-support] Re: Objects cached in FB memory

2019-06-21 Thread Karol Bieniaszewski liviusliv...@poczta.onet.pl [firebird-support]
Hi,

I do not suppose it is possible. But why do you need that info?

regards,
Karol Bieniaszewski


[firebird-support] Re: Objects cached in FB memory

2019-06-21 Thread m_brahi...@yahoo.fr [firebird-support]
I mean through the system tables I have FB 3

[firebird-support] Objects cached in FB memory

2019-06-21 Thread m_brahi...@yahoo.fr [firebird-support]
Hi All,

Is it possible please to see by sql what is cached in FB memory some DBMS does 
it.
Thanks
 



Re: [firebird-support] index vs page size

2019-06-21 Thread Nick Upson n...@telensa.com [firebird-support]
Thank you



Kind Regards,
Nick

Nick Upson | Principal Operations Engineer
office +44 01799 588800 support hotline +44 1799 399200
DDI +44 01799 588621

telensa.com | @telensa 
| Linkedin



From: firebird-support@yahoogroups.com  on 
behalf of Ann Harrison aharri...@ibphoenix.com [firebird-support] 

Sent: 21 June 2019 12:31
To: firebird-support@yahoogroups.com
Subject: Re: [firebird-support] index vs page size




On Jun 20, 2019, at 11:10 AM, Nick Upson 
n...@telensa.com [firebird-support] 
mailto:firebird-support@yahoogroups.com>> 
wrote:

Hi

I have a large 100Gb+ firebird 2.5 database and I'm trying to deal with some 
performance issues.

One indicator I have found is that several large tables have indexes with a 
depth of 3 (and one of 4). The guidance I have seen says to increase the page 
size until the depth is below 3 but the pagesize is already maxed out at 16k. 
Can anyone suggest other actions I could take.

The guidance should have been three or less, not less than three.  One index 
with four levels should not be a crisis if you have adequate page cache.

Good luck,

Ann




Kind Regards,
Nick

Nick Upson | Principal Operations Engineer
office +44 01799 588800 support hotline +44 1799 399200
DDI +44 01799 588621

telensa.com | @telensa 
| Linkedin


IMPORTANT NOTICE: This e-mail message is intended to be received only by 
persons entitled to receive the confidential information it may contain. E-mail 
messages to clients of Telensa may contain information that is confidential and 
legally privileged. Please do not read, copy, forward, or store this message 
unless you are an intended recipient of it. If you have received this message 
in error, please forward it to the sender and delete it completely from your 
computer system.


CAUTION. This email originated from outside of Telensa. Do not click links or 
open attachments unless you recognise the sender and know the content is safe.
IMPORTANT NOTICE: This e-mail message is intended to be received only by 
persons entitled to receive the confidential information it may contain. E-mail 
messages to clients of Telensa may contain information that is confidential and 
legally privileged. Please do not read, copy, forward, or store this message 
unless you are an intended recipient of it. If you have received this message 
in error, please forward it to the sender and delete it completely from your 
computer system.


Re: [firebird-support] index vs page size

2019-06-21 Thread Ann Harrison aharri...@ibphoenix.com [firebird-support]


> On Jun 20, 2019, at 11:10 AM, Nick Upson n...@telensa.com [firebird-support] 
>  wrote:
> 
> 
> 
> Hi
> 
> I have a large 100Gb+ firebird 2.5 database and I'm trying to deal with some 
> performance issues.
> 
> One indicator I have found is that several large tables have indexes with a 
> depth of 3 (and one of 4). The guidance I have seen says to increase the page 
> size until the depth is below 3 but the pagesize is already maxed out at 16k. 
> Can anyone suggest other actions I could take.

The guidance should have been three or less, not less than three.  One index 
with four levels should not be a crisis if you have adequate page cache. 

Good luck,

Ann



> Kind Regards,
> Nick
> 
> Nick Upson | Principal Operations Engineer
> office +44 01799 588800 support hotline +44 1799 399200
> DDI +44 01799 588621
> telensa.com | @telensa | Linkedin
> 
> IMPORTANT NOTICE: This e-mail message is intended to be received only by 
> persons entitled to receive the confidential information it may contain. 
> E-mail messages to clients of Telensa may contain information that is 
> confidential and legally privileged. Please do not read, copy, forward, or 
> store this message unless you are an intended recipient of it. If you have 
> received this message in error, please forward it to the sender and delete it 
> completely from your computer system. 
> 
>