tt connect : low print output performance on socket connection
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 113
- Forks
- 18
- Avg merge
- 4d 11h
- Merged PRs (30d)
- 23
Description
require("fun").ones():take(50000):totable()
Works very slowly for large objects
Of course, there is no need in itself to print large objects
But sometimes it happens by misclick that causes it to freeze
For comparison native tarantool console work almost instantly
https://github.com/tarantool/docker/blob/master/files/console
tarantoolctl connect also work good
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the large-object output case from the issue, then compare the socket output path used by tt connect with the linked native tarantool console and tarantoolctl connect implementations. Done means the provided 50,000-item example no longer freezes and output performance is comparable to those reference commands.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, lua
- Domain
- cli, performance
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100