Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MongoDB perfmonitor.har collections grows too big #8

Open
leibowitz opened this issue Jun 10, 2013 · 2 comments
Open

MongoDB perfmonitor.har collections grows too big #8

leibowitz opened this issue Jun 10, 2013 · 2 comments

Comments

@leibowitz
Copy link
Owner

Using mongoDB default settings it will pre-allocate files for the collection which will double in size each time, ie 256M, 512M, 1024M, etc. eventually ending up generating huge files on the disk.

This method is normally used to improve performance but in this case can potentially make your server run out of space quickly, as the size of all the HAR files generated for each tests can end up being quite large

@leibowitz
Copy link
Owner Author

using capped collection is one solution, but would require storing the load time in a different collection (see milestone)

In the meantime you tweak MongoDB config, to use smallfiles for example

@leibowitz
Copy link
Owner Author

WIP in the db-timings branch to store data to a separate collection. This can cause issue when using a capped collection though, as it will mean the records in both collection won't have the same data.

To solve this issue it will be necessary to use a TTL collection instead where each record has a certain time expiry.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant