Brandon Ros
Brandon Ros
I'd be curious to see rudimentary operations per second on normal benchmarks like, fibonacci? Obviously nobody implementing a performant fibonacci application would stand up a Postgre instance and add this...
This project is very interesting and it is reassuring to hear your response that the overhead should not be too high. Out of curiosity, what did you write this project...
`docker run -d --name postgres clkao/postgres-plv8:latest` `docker exec -it postgres bash -c 'psql -U postgres -c "CREATE EXTENSION plv8;"'` `docker run --rm -p 3000:3000 -e PGRST_DB_URI="postgres://postgres@postgres/postgres" -e PGRST_DB_ANON_ROLE="postgres" -e PGRST_DB_SCHEMA="public"...
0.391 ms for the plv8 fibonnacci implementation versus 0.09ms for the node.js version? What could be the cause for that overhead?
Can this be closed?
@peoro is this the case with v12 as well?
https://github.com/andywer/leakage/pull/36 Does this fix it?
Can we refactor package to use https://nodejs.org/api/v8.html#v8_v8_getheapstatistics instead of memwatch?
> as memwatch also provides the heap snapshot diffing Can you outline what that would look like in a `require('v8').getHeapStatistics()` world?
node officially releasing the importable ‘v8’ library threw things off a bit, I’d imagine