mirror of https://github.com/logos-co/roadmap.git
remove duplicates
This commit is contained in:
parent
c9adc9486c
commit
5ed75d1f83
|
@ -53,14 +53,6 @@ draft: false
|
||||||
- _achieved_: Optimize _select_/_Store_ queries by adding prepared statements. [PR](https://github.com/waku-org/nwaku/pull/2182)
|
- _achieved_: Optimize _select_/_Store_ queries by adding prepared statements. [PR](https://github.com/waku-org/nwaku/pull/2182)
|
||||||
- _next_: Wrap up the Postgres optimizations. Summarize the performance comparison in a report.
|
- _next_: Wrap up the Postgres optimizations. Summarize the performance comparison in a report.
|
||||||
|
|
||||||
**[nwaku] [PostgreSQL](https://github.com/waku-org/nwaku/issues/1888)**
|
|
||||||
|
|
||||||
- _achieved_:
|
|
||||||
- Time processing enhancement when performing _SELECT_ operations. There was an overhead caused by looping too many times over the returned rows, in order to convert the row types. By applying a "rowCallback" approach we can reduce by 30ms the time spent on the query under analysis.
|
|
||||||
- _next_:
|
|
||||||
- The queries used in the comparison analysis still perform much better in _SQLite_ (< ~5ms) than in _Postgres_ (< ~15ms.) Therefore we need to push the investigation further to enhance that.
|
|
||||||
( Edited: notice that the timings indicated above are for tests using consecutive queries. If the queries are performed concurrently, then the timings are worse. I will elaborate more in a report shortly .)
|
|
||||||
|
|
||||||
## [Waku Network Gen 0](https://github.com/waku-org/pm/issues/50) - 2023-12-01
|
## [Waku Network Gen 0](https://github.com/waku-org/pm/issues/50) - 2023-12-01
|
||||||
|
|
||||||
|
|
||||||
|
@ -93,21 +85,6 @@ draft: false
|
||||||
- finalize the SQLite `messageHash` attribute and add a research page about it.
|
- finalize the SQLite `messageHash` attribute and add a research page about it.
|
||||||
- start a research page about the sync mechanism for nWaku, doing request/reply a PoC on the same.
|
- start a research page about the sync mechanism for nWaku, doing request/reply a PoC on the same.
|
||||||
|
|
||||||
### [2.1: Production testing of existing protocols](https://github.com/waku-org/pm/issues/49)
|
|
||||||
|
|
||||||
**[nwaku] [PostgreSQL](https://github.com/waku-org/nwaku/issues/1888)**
|
|
||||||
|
|
||||||
- _achieved_: Optimize _select_/_Store_ queries by adding prepared statements. [PR](https://github.com/waku-org/nwaku/pull/2182)
|
|
||||||
- _next_: Wrap up the Postgres optimizations. Summarize the performance comparison in a report.
|
|
||||||
|
|
||||||
**[nwaku] [PostgreSQL](https://github.com/waku-org/nwaku/issues/1888)**
|
|
||||||
|
|
||||||
- _achieved_:
|
|
||||||
- Time processing enhancement when performing _SELECT_ operations. There was an overhead caused by looping too many times over the returned rows, in order to convert the row types. By applying a "rowCallback" approach we can reduce by 30ms the time spent on the query under analysis.
|
|
||||||
- _next_:
|
|
||||||
- The queries used in the comparison analysis still perform much better in _SQLite_ (< ~5ms) than in _Postgres_ (< ~15ms.) Therefore we need to push the investigation further to enhance that.
|
|
||||||
( Edited: notice that the timings indicated above are for tests using consecutive queries. If the queries are performed concurrently, then the timings are worse. I will elaborate more in a report shortly .)
|
|
||||||
|
|
||||||
## [Quality Assurance processes are in place](https://github.com/waku-org/pm/issues/73) - 2024-03-31
|
## [Quality Assurance processes are in place](https://github.com/waku-org/pm/issues/73) - 2024-03-31
|
||||||
|
|
||||||
## [Support Many Platforms](https://github.com/waku-org/pm/issues/42) - 2024-04-30
|
## [Support Many Platforms](https://github.com/waku-org/pm/issues/42) - 2024-04-30
|
||||||
|
|
Loading…
Reference in New Issue