microsoft / microsoft/go-sqlcmd
Evaluate stdout performance and experiment with buffered i/o for performance
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 595
- Forks
- 91
- Avg merge
- 9h 35m
- Merged PRs (30d)
- 1
Description
Go stdout is not buffered. Performance of printing large result sets is likely to be poor. Measure the performance and look at buffered i/o options, whether it's implementing our own buffer like the native sqlcmd does or switching to the bufio package to wrap stdout.
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 locating the code path that writes large result sets to stdout and measure its current performance. Compare the issue's proposed buffering options, including Go's bufio package and an implementation like native sqlcmd; done means the performance findings and chosen approach are clear.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, performance
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100