refactor: remove async remote write decode logic (#1631) ## Rationale Deserialization is a CPU-intensive task, so introducing async does not provide significant benefits. In addition, using async causes function contagion issues. Therefore, it is necessary to remove the async decode logic. ## Detailed Changes - Remove `decode_async` interface - Change the back-end object pool dependency from `deadpool` to `object-pool` - Change benchmark logic accordingly ## Test Plan Manual test
Apache HoraeDB (incubating) is a high-performance, distributed, cloud native time-series database.
[!IMPORTANT] Apache HoraeDB (incubating) is an effort undergoing incubation at the Apache Software Foundation (ASF), sponsored by the Apache Incubator PMC.
Please read the DISCLAIMER and a full explanation of “incubating”.
The main branch is used for developing new engine described in this RFC. It‘s currently in a phase of rapid development and remains somewhat unstable, and it’s scheduled to be publicly available towards the end of 2025.
The legacy, stable engine is in analytic-engine branch.
Thrive together in Apache HoraeDB (incubating) community with users and developers from all around the world.
Read our Contributing Guide and make your first contribution!
When develop we benefit a lot from several other open source projects, such as VictoriaMetrics, thanks for their awesome work.