◆ Elasticsearch

Improve search performance

This is real work, not a feature someone invented — it comes from real job ads and real questions people asked. Below are four ready AI prompts: get it done, make it easy for the next person to say yes to, work out the right move when you are stuck, and stop it coming back.

4prompts

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskRun the query to show the top 10 slowest search queries from the last 24 hours in the…+
Run the query to show the top 10 slowest search queries from the last 24 hours in the production cluster, and put the results in a CSV file called 'slow_queries_20240723.csv'.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
BImprove — make it easier to acceptBefore I push this new search feature to production, analyze the performance impact of the…+
Before I push this new search feature to production, analyze the performance impact of the updated query logic. Show me if the average response time for 'product_search' queries will increase by more than 100ms compared to the current version, and flag any new queries that hit more than 50% of the index shards.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentThe new product catalog search is live, but users are complaining about slow results, and I'm…+
The new product catalog search is live, but users are complaining about slow results, and I'm seeing intermittent timeouts on the API gateway.
The new product catalog search is live, but users are complaining about slow results, and I'm seeing intermittent timeouts on the API gateway. I'm afraid the recent index merge caused a hot spot, but I can't tell which shards are overloaded without causing more performance issues. What's the most likely cause for this sudden slowdown, and what's the safest way to diagnose the shard distribution without impacting user experience further?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI keep getting pulled into urgent performance incidents because of unexpected query spikes or…+
I keep getting pulled into urgent performance incidents because of unexpected query spikes or inefficient aggregations.
I keep getting pulled into urgent performance incidents because of unexpected query spikes or inefficient aggregations. We're always reacting. What habit should I change to proactively identify potential performance bottlenecks in new search features before they hit production, especially regarding complex aggregations and cross-index queries, so I stop losing entire afternoons to emergency fixes?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?

Questions people actually ask

honest answers, no sign-up

Every task here was seen in the real world. Someone doing the job named it, a real job ad asked for it, or a lot of people asked about it online.

If nothing real showed a task, it is not on the page. That is the whole rule.

They are the same job approached four ways, because what you need depends on where you are.

Get it done today. Make it easy for the next person to say yes to. Work out the right move when you are stuck. Learn the pattern so the job stops coming back.

For most of these jobs it can carry the heavy thinking - draft it, sort it, check it, rehearse it with you.

It cannot sit in your chair, take the blame when a number is wrong, or notice what nobody wrote down. Let it do the first 80%. Keep the last 20% that is truly yours.

No. Copy any prompt and paste it into the AI you already use. No account, no score, no wall in the way.

Any of them. The prompts describe the work rather than naming a product, so they are not tied to one assistant.

That is also why they keep working when you switch.

Change it freely. Every prompt is a starting line, not a rule.

Put in your real numbers, your real names and your real deadline. The more you make it yours, the better the answer comes back.

The tasks come from real job ads, published job data and the questions people ask in public forums.

The steps come from Elasticsearch's own documentation, with practitioner sources for the traps the manual does not mention.

Push once. Ask it to sharpen the weakest part and to say what it assumed.

Most wrong answers come from a missing detail rather than a bad prompt - tell it the thing it could not know.