Just looking at it, B is naively more computation (naively because I don't know much about the actual documents in the collection, just their shape).The two pipelines should always produce the same results, so if the latter is better, then use it, for now.We combine our matchmaker’s intuition with the information and feedback we’ve gathered from you in our conversations: what’s important to you, what’s worked, what hasn’t. Our matchmakers are committed to knowing their clients, not just on paper, but on a true human level thanks to our regular interaction and communication with you.Once we’ve selected your match, we’ll call and share with you details about who we’ve chosen.Because, in the end, meeting someone face-to-face is the only way to see if sparks fly.It all starts with a phone call – a confidential conversation during which one of our dating specialists can answer your questions and give you more details about the It’s Just Lunch dating process. We’ll learn what you’re looking for in a potential partner, what’s worked for you in past relationships and – just as importantly – what hasn’t worked.
Then using our signature matchmaking process that we’ve fine-tuned over the past 25 years, we create a dating experience personalized just for you.
In query B, Mongo reduce result to smaller data set, and than apply campaign_name on that, so it's faster and does not go over other shards.
Just i was expecting that Mongo DB can figure out that automatically :) That's surprising.
Deciding when to have "the talk" can be anxiety-inducing, even relationship-ending before it even has had the chance to start. (Getty Images)There are always new challenges to dating, especially in the digital age. Looking for someone who enjoys the “simpler” things in life, maybe like small town living?
Query A take about 0.35 sec to be executed, and query B take about 1.1 sec, and they both return same result.
Think of us as your dating concierge and leave the details to us.