![]() | ![]() Products ![]() ![]() ![]() ![]() |
Home » Technical Support » ElevateDB Technical Support » Support Forums » ElevateDB General » View Thread |
Messages 1 to 6 of 6 total |
![]() |
Thu, Jan 10 2019 12:57 AM | Permanent Link |
Ian Branch |
Attachments: Screenshot_6.jpg |
Thu, Jan 10 2019 2:30 AM | Permanent Link |
Roy Lambert NLH Associates ![]() | Ian
Its what I'd expect from a buffering operation. The whole point of buffering is to speed things up and you don't want to be slowing it down by opening / closing files just because they're not in use at the moment. Roy Lambert |
Thu, Jan 10 2019 3:55 AM | Permanent Link |
Ian Branch | Roy Lambert wrote:
> not in use at the moment. Hi Roy, Surely they should be released at some time? Ian |
Thu, Jan 10 2019 5:17 AM | Permanent Link |
Roy Lambert NLH Associates ![]() | Ian
When the engine closes. Roy Lambert |
Thu, Jan 10 2019 9:02 AM | Permanent Link |
Raul ![]() | On 1/10/2019 5:17 AM, Roy Lambert wrote:
> When the engine closes. As Roy said - EDBServer should keep files locked as long as it runs - shutting down EDBServer service should release those files. The whole idea of I/O Buffering is to have exclusive access to files being buffered and load them into memory and keep them there (as per settings) - catalog, config and actual tables. This way as apps connect/disconnect there is minimal, if any, disk I/O needed resulting in better performance. Raul |
Fri, Jan 11 2019 11:41 AM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. ![]() |
This web page was last updated on Monday, June 17, 2024 at 07:11 AM | Privacy Policy![]() © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? ![]() |