RisingWave Labs
-
|
For instance, I create a materialized view of pg with a high tps and make a complex aggregative query on it. How does risingwave process the load? Do they share cpu of the same cluster component? |
Beta Was this translation helpful? Give feedback.
Answered by
yingjunwu
Dec 3, 2022
Replies: 1 comment
-
|
No RisingWave does not isolate streaming workload (aka MV workload) from ad-hoc query workload. So if you have an intensive ad-hoc query workload, then stream processing will suffer, resulting in staled MV. The quick fix you may apply is to provision separate clusters - one for streaming and one for ad-hoc queries. |
Beta Was this translation helpful? Give feedback.
0 replies
Answer selected by
doki23
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
No RisingWave does not isolate streaming workload (aka MV workload) from ad-hoc query workload. So if you have an intensive ad-hoc query workload, then stream processing will suffer, resulting in staled MV. The quick fix you may apply is to provision separate clusters - one for streaming and one for ad-hoc queries.