I have Postgres 9.1 installed on Windows server 2008 R2 machine having 32 GB RAM. For performance tuning i have to update the shared buffer to 8 GB. But after updating the shared buffer to 8 GB in postgresql.conf file i am not able to start the service. its giving error message "The Postgresql-9.1 - Postgresql server 9.1 serviceon local computer started and then stopped. Some servcies stop automatically if they are not in use by other servcies or programs".
Any one can suggest how can i update the shared buffer. your suggestions are highly appreciated...
Related
We are using, PostgreSQL Version 14.
Our PC configuration at production
Windows 2016 Server
32 GB RAM
8 TB Hard disk
8 Core CPU
In my PostgreSQL.conf file
Shared_buffer 8 GB
Work_MEM 1 GB
Maintenance_work_mem 1 GB
Max_Connections 1000
I wish to handle 5000 connection at a time. Somebody suggest me to go with PGBouncer.
But we initially starts with PostgreSQL without PGBouncer.
I need to know, is my configuration is OK with the 5000 connection or we need to increase RAM or any other...
This is our first, PostgreSQL implementation. So Please suggest me to start with PostgreSQL with out PGBouncer.
Thank you
Note:
In SQL if we set -1, it will handle more number of connections. Like this is there any configuration is available in PostgreSQL
Creating a new empty database (using pgAdmin 4) usually takes 5-15 sec but recently it started to take much longer (2-3min).
When creating a new database I use a template (postgis) database. We have recently switched from postgresql 9 to 10.
Anticipating potential questions:
template database is empty (only template tables etc)
I did the VACUUM FULL
the database server (Win server 2012, Intel Xeon 3,2 Ghz 12 cores, 64GB RAM) is not very overloaded - on average: 7-10% CPU, 30-35% memory usage
Any hints what might be the reason? what elese should I check ?
I have installed Firebird 3.0.2 SQL database on my Windows Server 2016. No other software has been installed yet.
I'm using Superserver mode and an SSD drive.
When I just copy my database file of size 6 GB, it is done in 20-30 seconds (same disk).
But when I execute backup it takes 20-30 minutes. Restore is about the same amount of time. Together 40-60 minutes.
And there is strange thing: backup/restore process (gbak.exe) does not use full power of CPUs and HDD. It is using only ~20% . I don't understand why.
I think it should be something in configuration right? But I kept everything in default values.
Very important thing: I am new in Windows Server 2016 so I have no idea what I am doing.
Any ideas?
I found out that it is about configuration of Power Options.
Windows Server 2016 is after installation set for Balanced Power Plan.
I changed it to High performance and results are highly better. (backup drops from 30 minutes to 6 minutes)
More details you can find here: https://serverfault.com/a/797473
To find the restore bottleneck in Firebird 3 you should add the detail protokoll option:
-v -stat TDRW Filename
-v (Verbose output of what GBAK is doing)
-stat (Runtime statistics in its verbose output)
T (Total time)
D (Total delta)
R (Page reads)
W (Page writes)
Have a look to the GBAK option
-service localhost:service_mgr
it is a speed demon :-)
I have a problem with postgres not being able to start:
* Starting PostgreSQL 9.5 database server * The PostgreSQL server failed to start. Please check the log output:
2016-08-25 04:20:53 EDT [1763-1] FATAL: could not map anonymous shared memory: Cannot allocate memory
2016-08-25 04:20:53 EDT [1763-2] HINT: This error usually means that PostgreSQL's request for a shared memory segment exceeded available memory, swap space, or huge pages. To reduce the request size (currently 1124007936 bytes), reduce PostgreSQL's shared memory usage, perhaps by reducing shared_buffers or max_connections.
This is the response that I got. I checked the log in tail -f /var/log/postgresql/postgresql-9.5-main.logand I can see the same response.
Can someone suggest what can be the problem?
I used following commands to stop/start the postgres server on Ubuntu 14.04 with postgres 9.5:
sudo service postgresql stop
sudo service postgresql start
As other people suggested, the error was only memory. I increased droplet memory on Digital Ocean and it fixed it.
I am running an application how reads and write a batch process using MongoDb in 2 identical machines. One running Windows 8.1 and the other running Windows Server 2012.
The MongoDb performance in the Windows Server 2012 machine is 5 times worse than Windows 8.
Both machines have 16Gb of RAM, but the mongod.exe process consumes 1.2Gb RAM in Windows 8 and 500Mb in Windows server in an identical local database.
I already use MongoDb 2.4, 2.6 and 2.6 legacy and de behavior is the same.
Has anyone seen this behavior before?