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

findOne is slow if collection transform is adding big fields #253

Open
namirsab opened this issue Nov 1, 2016 · 2 comments
Open

findOne is slow if collection transform is adding big fields #253

namirsab opened this issue Nov 1, 2016 · 2 comments

Comments

@namirsab
Copy link

namirsab commented Nov 1, 2016

Observed Behavior

After the latest release (2.30.2) I've realized one of my collections was performing much slower when finding documents ( from ms to 3-4 seconds). To fix it, I had to reduce the transform of the document to a simpler object.

Expected Behavior

Kadira does not make the app that slower when finding documents in the database.

Reproduce by

Create a transform that adds a big field to a collection.
Measure the time to find a document

@arunoda

@namirsab
Copy link
Author

namirsab commented Nov 1, 2016

I believe you are stringifying the document or something like this on every findOne, meaning that if the object is big enough, it will take a lot of time.

But this was not happening before the latest release, so I wonder if #144 is related

@lampe
Copy link

lampe commented Nov 1, 2016

👍

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

2 participants