I am evaluating MongoDB, to work with a large data set around 10 GB.
My search took me to this post
http://edgystuff.tumblr.com/post/49304254688/how-to-use-mongodb-as-a-pure-in-memory-db-redis
Which says that if we have enough RAM memory, then MongoDB automatically will start working as InMemory Database, on Linux
Would MongoDB behave similarly on Windows Server 2012 R2 ?
With minimal or zero tweaking, would MongoDB work as InMemory DB, if we have sufficient RAM ?
Thanks
ameet
Related
I have several databases under the mongodb instance (v 4.0.26) in a Ubuntu 18.04 server.
One of the database has started behaving inconsistently in terms of connectivity all of a sudden.
I have checked the resource consumption on the server. 7GB of RAM left and 34GB of storage also available.
In Mongo Shell (at the server), when I connect to the particular database and perform db.getCollectionNames() it just hangs. This behavior is also not consistent. But every other database in that instance works without any problem.
I am suspecting there could be a corrupt document in any of the collection which is resulting this. Looking for guidance to debug this issue.
P.S.: Losing the data in db might cost my job.
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 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?
I am using mongodb-v2.0. I have gone through the 32-bit mongodb limitation of "2GB". The thing which baffling me is 2GB limitation. I will explain our scenario :-
When the database reaches 2GB. It is possible to use different database name in a single instance.If so then each database will have 2GB? Can we use different instance of mongodb listening on different port. If its possible,then can we continue in creating new database until it reaches 2GB of size?. In this way can we use multiple database of size 2GB on 32-bit mongodb on 32-bit machines?
Thanks,
sampath
The 2GB are the storage limit for the mongodb server. See in the FAQ http://www.mongodb.org/display/DOCS/FAQ#FAQ-Whatarethe32bitlimitations%3F
But maybe this is your solution: Database over 2GB in MongoDB