Log file Viewer

[13:23:11] <helmut4k> Hello!

[13:24:05] <helmut4k> I am using MongoDB 4 and have a problem with slow queries, and I come here to ask, if anybody can give me a hint to fix it.

[13:25:15] <helmut4k> I'll try to delete many files in batches of 100, with average filesize of 2MB

[13:25:52] <helmut4k> MongDB is running on a debian system with ext4 filesystem

[13:25:59] <GothAlice> helmut4k: https://docs.mongodb.com/manual/tutorial/analyze-query-plan/ + https://studio3t.com/knowledge-base/articles/mongodb-query-performance/ + https://www.compose.com/articles/explain-explain-understanding-mongo-query-behavior/

[13:26:38] <helmut4k> here is an example of the log: https://pastebin.com/iMMGzLYm

[13:26:41] <GothAlice> In general I avoid ext* based filesystems due to hard limits on the number of individual inodes (e.g. you can "run out of disk space" by simply having too many files by count, not by space consumed) and slow (exhaustive) repairs.

[13:28:22] <GothAlice> See also: https://gist.github.com/amcgregor/4fb7052ce3166e2612ab#memory regarding ensuring your servers have sufficient RAM to (at a minimum) have the indexes persistent in memory and "transparent huge pages", which can seriously cut into performance. (As a malloc() call won't be allocating 4KB chunks of memory, it could allocate gigabytes… as single chunks.)

[13:30:45] <helmut4k> thank you GothAlice

[13:40:49] <helmut4k> GothAlice: yes could be related with RAM

[13:41:13] <helmut4k> Did you read the pasted log, is there anything special in it?

[13:54:45] <GothAlice> Alas, I can't look into your specific logs at the moment.

[14:02:23] <helmut4k> okay, thanks anyway, maybe at later moment :3

[14:41:35] <me1t> Hey gang. I'm trying to restore a backup taken with mongodump --archive, and I'm using mongorestore. I get Failed: file mongo.storagea.20190528.archive does not have .bson extension and the file seems to be a binary file. How do I get mongorestore to restore it?

[14:42:08] <me1t> Thanks, by the way.