# Writing fast s3Cluster queries

Optimize your query performance to get faster results when exploring your raw events.

## Running the same query repeatedly?

Extract values as **non-aggregated fields** in **Warehouse** -> [Sources](https://warehouse.betterstack.com/team/0/sources ";_blank") -> Your source -> **Time series on NVMe SSD** instead of querying raw JSON events each time. This converts your frequently-accessed events into time series metrics for much faster retrieval.

Learn more about [Extracting time series from events](https://betterstack.com/docs/logs/dashboards/logs-to-metrics/).

## Understanding your data types

Our infrastructure handles **JSON events** and **time series** differently, with metrics offering much faster query performance. Learn more about [JSON events vs. time series](https://betterstack.com/docs/logs/wide-events-time-series/).

If you're frequently running the same queries, consider whether your use case would benefit from [converting events to time series](https://betterstack.com/docs/logs/dashboards/logs-to-metrics/).

### When to use time series vs. JSON events

**Use time series when**

- Running the same query repeatedly.
- Need sub-second query performance.
- Working with numerical data and aggregations.

**Use JSON events when**

- Performing ad-hoc exploration.
- Need full context and details.
- Debugging specific issues.
- Working with unstructured data.

## Optimizing ad-hoc event queries

For faster queries on your **JSON events**, try these optimization techniques:

### 1. Narrow your time range

Shorter time frames significantly reduce the amount of data processed.

![Narrowing the time range](https://imagedelivery.net/xZXo0QFi-1_4Zimer-T0XQ/0180de4c-9f93-4eb5-30f5-9cff5d115900/orig =2166x878)

### 2. Make your s3Cluster function more specific

```sql
[label Using more specific WHERE clause with the s3cluster function]
SELECT dt, raw
FROM (
  SELECT dt, raw
  FROM remote(t123456_your_source_logs)
  UNION ALL
  SELECT dt, raw
  FROM s3Cluster(primary, t123456_your_source_s3)
  WHERE _row_type = 1 -- include as many filters here, in the inner query  
)
WHERE raw LIKE '%My text%'
ORDER BY dt ASC
LIMIT 5000
FORMAT JSONEachRow

```

### 3. Query specific sources

Instead of searching across all sources, target the specific source containing your data.

- Select individual sources in the source dropdown.
- Avoid querying All sources when possible.

![Querying a single source](https://imagedelivery.net/xZXo0QFi-1_4Zimer-T0XQ/0a66e4c6-4a06-40db-3a21-7f1014e3fa00/lg1x =2166x878)

### 4. Use sampling for exploration

Enable Sampling to work with a representative subset of your data while developing and testing queries.

![Using sampling](https://imagedelivery.net/xZXo0QFi-1_4Zimer-T0XQ/b5e07771-d7d1-42f3-a1e9-cb3549983f00/public =1708x1430)

### 5. Request additional compute

For consistently slow queries on large datasets, we can add more compute power to your cluster:

- Share a slow query link with our support team.
- We'll analyze your data volume and query performance.
- Small adjustments are often available at no charge.
- Larger performance improvements for very large datasets may require a custom cluster for an additional cost.

## Custom clusters for high performance

For applications requiring consistently fast queries over large datasets and long time periods, we can provision dedicated compute resources:

- **Tailored setup**: Custom cluster sized for your specific needs.
- **Dedicated compute**: No resource sharing with other workloads.
- **Faster speeds**: Optimized for your query patterns and data volume.
- **Additional cost**: Comes with dedicated infrastructure pricing.

Contact our support team at hello@betterstack.com to discuss custom cluster options for your use case 📩

## Getting help

Generally speaking, we can make querying as fast as needed through query optimization or infrastructure scaling. If you're experiencing slow query performance:

1. Try the optimization techniques above.
2. Share a slow Logs & traces link with our support team using the in-app chat or at hello@betterstack.com.
3. Describe your performance requirements and use case.

**We're happy to help find the right balance of performance and cost for your needs** 🚀

![Better Stack support team](https://imagedelivery.net/xZXo0QFi-1_4Zimer-T0XQ/e690f898-5c3d-4ca0-c008-ad820bff3700/public =2170x2134)