[SERVER-517] yield on long running query Created: 02/Jan/10  Updated: 12/Jul/16  Resolved: 22/Jun/10

Status: Closed
Project: Core Server
Component/s: Concurrency
Affects Version/s: None
Fix Version/s: 1.5.4

Type: Improvement Priority: Major - P3
Reporter: Eliot Horowitz (Inactive) Assignee: Eliot Horowitz (Inactive)
Resolution: Done Votes: 23
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-797 better way to generate clientcursor Closed
Participants:

 Description   

This will REALLY happen in 1.5.4
Will do it first so it can't slip



 Comments   
Comment by auto [ 22/Jun/10 ]

Author:

{'login': 'erh', 'name': 'Eliot Horowitz', 'email': 'eliot@10gen.com'}

Message: yield based off of scanned and time
ElapsedTracker class for managing (horrible name)
finish SERVER-517
http://github.com/mongodb/mongo/commit/14344eeea3858c07f627a29ee7a6ad2e06b05d35

Comment by auto [ 22/Jun/10 ]

Author:

{'login': 'erh', 'name': 'Eliot Horowitz', 'email': 'eliot@10gen.com'}

Message: don't yield if you're a reader and only other readers are active SERVER-517
http://github.com/mongodb/mongo/commit/fd3b8fa7adf62c7833b12a87c8e4693c7e2fec9a

Comment by auto [ 22/Jun/10 ]

Author:

{'login': 'erh', 'name': 'Eliot Horowitz', 'email': 'eliot@10gen.com'}

Message: yield on long running queries basics SERVER-517
http://github.com/mongodb/mongo/commit/2b251ff7f626d67b3fc9e6e9de76092985981c20

Comment by Dwight Merriman [ 02/Mar/10 ]

MongoDB queries allow substantial interleaving of other operations when the query returns a lot of data. However when scanning and not returning data, the read lock is held. This could be periodically released (yield) to allow more interleaving of operations.

Generated at Thu Feb 08 02:54:22 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.