PostgreSql 10.1 memory usage very high after upgrading to Orthanc 1.5.1 on Windows 2008 R2

Google Groups archive
1

I’m experiencing very high memory usage ever since upgrading to Orthanc 1.5.1. On Windows start up, ram usage is around 5% but it gradually keeps increasing and will eventually balloon to where it is using almost all the ram.The DB size is only 4941MB. The server has 8gb total memory and is a Xeon Quad core. The DB is on its own SSD drive. Below are the settings from my postgresql.conf file:


max_connections = 200           
shared_buffers = 512MB          
work_mem = 6553kB               
maintenance_work_mem = 512MB
dynamic_shared_memory_type = windows    
max_worker_processes = 4        
max_parallel_workers_per_gather = 2 
max_parallel_workers = 4        
wal_level = hot_standby
wal_buffers = 16MB          
max_wal_size = 2GB
min_wal_size = 1GB
checkpoint_completion_target = 0.7  
max_wal_senders = 5
wal_keep_segments = 32
max_replication_slots = 5

Below is a screenshot of Task Manager....

Screenshot of Task Manager

If any other info is required i’ll happily provide it.

2

Hello Rana,

Large chunks of the Orthanc database-related source code have been rewritten quite recently (>= 1.5.2) :

Orthanc 1.5.2 is out! This maintenance release features new primitives to optimize database plugins in the presence of large datasets. It also comes with several fixes.

Please make sure you have the latest versions of Orthanc and the postgresql plugins before attempting any DB performance tuning.

If these problems remain after updating, you might want to try lowering the shared_buffers settings and instead rely on the OS cache. It often helps!

Let us know how it goes and, if you have some particular tip and tricks to optimize postgreSQL settings with Orthanc, it would be fantastic if you could share them with the community!

Cheers

3

Isnt version 1.5.1 the latest version for which Windows installer has been released ?

Untitled.png

4

Typo on the Web site: Osimis Installer 19.1.1 includes Orthanc 1.5.3.

This is now fixed.

S-