replace cedardb docker image with native cedardb and update measurements

[lukasvogel]

This also solves the troubles where the CedarDB docker container apparently didn't shut down within the time limit on larger instances as it hugely simplifies the whole setup.

[alexey-milovidov]

Thanks! Running it...
for system in cedardb; do for machine in c6a.4xlarge c6a.2xlarge c6a.xlarge c6a.large t3a.small c6a.metal c8g.4xlarge c8g.metal-48xl c7a.metal-48xl; do export machine=$machine system=$system repo=lukasvogel/ClickBench branch=newapproach; ./run-benchmark.sh; done; done

[alexey-milovidov]

It does not work:

Downloading https://download.cedardb.com/latest/cedar-current-amd64.tar.xz into /ClickBench/cedardb/cedar-current-amd64.tar.xz...

cedar/
cedar/cedardb
cedar/README.md
cedar/catalogupgrade

Preparing to install systemd units (scope: user)
  ExecStart=/ClickBench/cedardb/cedar/cedardb -createdb /ClickBench/cedardb/db -createSSLFiles
  ListenStream (unix): /tmp/.s.PGSQL.5432
  ListenStream (tcp):  127.0.0.1:5432 and [::1]:5432
Failed to connect to bus: No medium found

[lukasvogel]

@alexey-milovidov thanks for flagging that, I didn't see that there is a new script to automatically deploy the instances. Looks like that doesn't play nice with user scoped systemd services. I've updated the systemd service to be system-scoped. I did one trial run with a c6a.4xlarge instance and the results showed up in the clickhouse playground, so it should wor know!

[lukasvogel]

@alexey-milovidov did you have the chance to run it again?

[durner]

@alexey-milovidov @rschu1ze , any updates on this?