Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

StackOverflow Point

StackOverflow Point Navigation

  • Web Stories
  • Badges
  • Tags
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Web Stories
  • Badges
  • Tags
Home/ Questions/Q 1388
Alex Hales
  • 0
Alex HalesTeacher
Asked: May 30, 20222022-05-30T14:25:43+00:00 2022-05-30T14:25:43+00:00

database – Performance issue when querying time-based objects

  • 0

[ad_1]

I’m currently working on a mongoDB collection containing documents that looks like the following :

{ startTime : Date, endTime: Date, source: String, metaData: {}}

And my usecase is to retrieve all documents that is included within a queried time frame, such as my query looks like this :

db.myCollection.find(
    {
        $and: [
            {"source": aSource},
            {"startTime" : {$lte: timeFrame.end}},
            {"endTime" : {$gte: timeFrame.start}}
        ]
    }
).sort({ "startTime" : 1 })

With an index defined as the following :

    db.myCollection.createIndex( { "source" : 1, "startTime": 1, "endTime": 1 } );

The problem is that queries are very slow (multiple hundreds of ms on a local database) as soon as the number of document per source increase.

Using mongo explain shows me that i’m efficiently using this index (only found documents are scanned, otherwise only index-access is made), so the slowness seems to come from the index scan itself, as this query needs to go over a large portion of this index.

In addition to that, such an index gets huge pretty quickly and therefore seems inefficient.

Is there anything i’m missing that could help makes those queries faster, or am I condemned to retrieve all the documents belonging to a given source as the best way to go ? I see that mongo now provides some time-series features, could that bring any help in regard of my problem ?

[ad_2]

  • 0 0 Answers
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report
Leave an answer

Leave an answer
Cancel reply

Browse

Sidebar

Ask A Question

Related Questions

  • xcode - Can you build dynamic libraries for iOS and ...

    • 0 Answers
  • bash - How to check if a process id (PID) ...

    • 4778 Answers
  • database - Oracle: Changing VARCHAR2 column to CLOB

    • 1063 Answers
  • What's the difference between HEAD, working tree and index, in ...

    • 1009 Answers
  • Amazon EC2 Free tier - how many instances can I ...

    • 0 Answers

Stats

  • Questions : 43k

Subscribe

Login

Forgot Password?

Footer

Follow

© 2022 Stackoverflow Point. All Rights Reserved.

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.