Issue Details (XML | Word | Printable)

Key: CORE-3560
Type: Bug Bug
Status: Reopened Reopened
Priority: Major Major
Assignee: Alexander Peshkov
Reporter: Jesus Angel Garcia Zarco
Votes: 0
Watchers: 6

If you were logged in you would be able to see more operations.
Firebird Core

Firebird 2.5 Classic Server uses 47% more memory than 2.1.5 when caching metadata

Created: 20/Jul/11 11:12 AM   Updated: 12/Jun/14 07:37 AM
Component/s: Engine
Affects Version/s: 2.5.0
Fix Version/s: None

File Attachments: 1. File Database.rar (8.92 MB)
2. File Gestlab_medatata_wo_udf.rar (1.99 MB)
3. File gestlab_metadata.rar (2.10 MB)
4. Microsoft Word MemoryUsageWindows.docx (790 kB)
5. File metadata.rar (821 kB)
6. File Multiconexion.rar (594 kB)
7. File UDFCointec.dll (320 kB)

Image Attachments:

1. ResourceMonitor.png
(107 kB)

2. TaskManager.png
(111 kB)

3. TaskManager.png
(111 kB)
Environment: Windows family

Sub-Tasks  All   Open   

 Description  « Hide
When the user connects to my application, executes one stored procedure to register the user login. This stored procedure update one table that force the load of most of the metadata in memory.

The difference is that while Firebird 2.1.5 uses 57100 Kb, Fb 2.5.1 uses 84100 Kb, that is a 47% more memory than 2.1. once executed the procedure and starting to work with the application, the memory consumption increases in parallel. That implies that for 200 users the less memory needed for 2.5 is near 16 Gb, while for 2.1 is near 11 Gb that is a big difference.

That implies that classic server will use per connection so much memory. I don't know if is a bug or not, but the difference is so much. If classic server is for complex enviroments with high load, then

Steps to reproduce the issue: Connect to the database and execute procedure usuario_entrada( 0, '', 'STATION01', '' )

 All   Comments   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
There are no subversion log entries for this issue yet.