tonista / hyrise Goto Github PK

Make an option for debug execution message. Previous one was:

Execution info: [PARSE: 93 µs 778 ns, SQL TRANSLATE: 79 µs 129 ns, OPTIMIZE: 129 µs 175 ns, LQP TRANSLATE: 66 µs 860 ns, EXECUTE: 455 µs 653 ns (wall time) | QUERY PLAN CACHE HITS: 0/1 statement(s)]

Python or C++
IF (C++) {
integrate in existing benchmark runner?
}

Potential errors:

• Socket-based:

• Port already in use

• New connection could not be created

• R/W: stream already closed

• SQL-based for simple queries:

• Invalid SQL

• Valid SQL, but other error (such as table not existing)

• Other pipeline errors handled in SQLPipelineStatus

• SQL-based for prep. statements:

• Invalid SQL

• Valid SQL, but other error (e.g. table not existing)

• Invalid parameter (such as string instead of float) (Can't handle this so far)

• Wrong number of params

• Other pipeline errors handled in SQLPipelineStatus (not applicable for prep. statements)

make NUMA-pinning compatible with numactl

Check compatibility with Boost.Asio 1.70

Flags for:

• Port
• Execution time message
• NUMA core pinning
• generate TPCH
• help

Namely:

• hyrise#1357
• hyrise#1032
• hyrise#853
• hyrise#1182

https://github.com/hyrise/hyrise/wiki/Networking

Noticed performance decrease after merging master once again.
Example SELECT 1;: 58µs --> 85µs (-47 %)

When executing queries in parallel, make sure we have correct isolation level