query: An alternative approach to the close queue
positive_passages.docid: 8156
positive_passages.text: Huge close votes review queue on Stack Overflow
negative_passages.docid: 14069
negative_passages.text: Niceness and Priority of Processes
negative_passages.docid: 1603
negative_passages.text: Loading next item from the close vote queue takes longer and longer
negative_passages.docid: 27542
negative_passages.text: How do I implement basic "Long Polling"?
negative_passages.docid: 79610
negative_passages.text: 'Followers' and efficiency
negative_passages.docid: 15588
negative_passages.text: Introduce a  "general reference" close reason
negative_passages.docid: 4175
negative_passages.text: Review Queues and Ignored Tags
negative_passages.docid: 31654
negative_passages.text: Closing Etiquette: Why Do Some Answer *and* Close?
negative_passages.docid: 22831
negative_passages.text: Changes to "close as duplicate" (part deux)
negative_passages.docid: 129118
negative_passages.text: Improving Review Queues - Design overview II: Changing review bans and other new features
negative_passages.docid: 17797
negative_passages.text: How about a "Vote not to close" option to counter the "Vote to close"?
negative_passages.docid: 6469
negative_passages.text: How costly is opening and closing of a DB connection?
negative_passages.docid: 124663
negative_passages.text: Priority queue in .Net
negative_passages.docid: 64511
negative_passages.text: A weighted version of random.choice
negative_passages.docid: 22817
negative_passages.text: Show sub reasons in close review queue
negative_passages.docid: 5819
negative_passages.text: Code to simulate deadlock
negative_passages.docid: 143390
negative_passages.text: Querying Time-based Workflow Queue