[BUG] Displaying fat rows / tall columns is objectively too slow

Open
#58 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
go
Domain
cli, performance

Research direction

Start by running the two provided ./stackql Snowflake commands and comparing their timings, using the referenced screen capture as context. Trace the output handling path for the fat-row and tall-column cases, then add or run benchmarks covering both queries; done means their processing time is demonstrably improved.

Written by the indexing model from the issue text.

Description

bug v0.4

Describe the bug

The output handling system does not process fat rows and tall columns in a timely fashion. Probably need to add benchmarks for this stuff into testing workflows. Please see screen capture.

Screen Shot 2023-01-29 at 12 22 49 pm

To Reproduce


time ./stackql --auth="${AUTH_STR_SNOWFLAKE}" --registry="${REG_TEST}" "${TLS_CFG}"  exec "select id from google.compute.instances where project = 'stackql-demo' and zone = 'australia-southeast1-a' limit 1;" > /dev/null


time ./stackql --auth="${AUTH_STR_SNOWFLAKE}" --registry="${REG_TEST}" "${TLS_CFG}"  exec "select * from google.compute.instances where project = 'stackql-demo' and zone = 'australia-southeast1-a' limit 1;" > /dev/null

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

  • OS: [e.g. iOS]
  • Browser [e.g. chrome, safari]
  • Version [e.g. 22]

Smartphone (please complete the following information):

  • Device: [e.g. iPhone6]
  • OS: [e.g. iOS8.1]
  • Browser [e.g. stock browser, safari]
  • Version [e.g. 22]

Additional context
Add any other context about the problem here.

Dominant language
Go
Stars
0
Forks
0
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from stackql/stackql-devel

All issues in stackql/stackql-devel

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.