## Is your feature request related to a problem?

If you have a trend with multiple lines, clickhouse queries for each are run one-after-another. If each takes 10s to calculate, then user will need to wait >30s in total.

## Describe the solution you'd like

Run queries in parallel.

## Describe alternatives you've considered

## Additional context

cc @EDsCODE @neilkakkar This seems like a quick win query-api wise though not 100% sure on how best implement this. Would you be up for prioritizing this _next_ sprint?

#### *Thank you* for your feature request – we love each and every one!

ee/clickhouse/queries/trends/clickhouse_trends.py
import copy
from itertools import accumulate
from typing import Any, Callable, Dict, List, Tuple
from django.db.models.query import Prefetch
from django.utils import timezone
from ee.clickhouse.client import sync_execute
from ee.clickhouse.queries.trends.breakdown import ClickhouseTrendsBreakdown
from ee.clickhouse.queries.trends.formula import ClickhouseTrendsFormula
from ee.clickhouse.queries.trends.lifecycle import ClickhouseLifecycle
from ee.clickhouse.queries.trends.total_volume import ClickhouseTrendsTotalVolume
from posthog.constants import TREND_FILTER_TYPE_ACTIONS, TRENDS_CUMULATIVE, TRENDS_LIFECYCLE
from posthog.models.action import Action
from posthog.models.action_step import ActionStep
from posthog.models.entity import Entity
from posthog.models.filters import Filter
from posthog.models.team import Team
from posthog.queries.base import handle_compare
from posthog.utils import relative_date_parse
class ClickhouseTrends(ClickhouseTrendsTotalVolume, ClickhouseLifecycle, ClickhouseTrendsFormula):