summaryrefslogtreecommitdiffstats
path: root/src/chunklist_test.go
AgeCommit message (Collapse)Author
2017-08-16Remove count field from ChunkListJunegunn Choi
2017-08-15Remove special nilItemJunegunn Choi
2017-07-16Reduce memory footprint of Item structJunegunn Choi
2017-07-16Remove pointer indirection by changing Chunk definitionJunegunn Choi
2016-09-18Revise ranking algorithmJunegunn Choi
2016-08-19Micro-optimizationsJunegunn Choi
- Make structs smaller - Introduce Result struct and use it to represent matched items instead of reusing Item struct for that purpose - Avoid unnecessary memory allocation - Avoid growing slice from the initial capacity - Code cleanup
2016-08-14[perf] Avoid allocating rune array for ascii stringJunegunn Choi
In the best case (all ascii), this reduces the memory footprint by 60% and the response time by 15% to 20%. In the worst case (every line has non-ascii characters), 3 to 4% overhead is observed.
2016-01-14Simplify Item structureJunegunn Choi
This commit compensates for the performance overhead from the extended tiebreak option.
2016-01-13Accept comma-separated list of sort criteriaJunegunn Choi
2015-08-02Performance fix - unnecessary rune convertion on --ansiJunegunn Choi
> time cat /tmp/list | fzf-0.10.1-darwin_amd64 --ansi -fqwerty > /dev/null real 0m4.364s user 0m8.231s sys 0m0.820s > time cat /tmp/list | fzf --ansi -fqwerty > /dev/null real 0m4.624s user 0m5.755s sys 0m0.732s
2015-08-02Performance tuning - eager rune array conversionJunegunn Choi
> wc -l /tmp/list2 2594098 /tmp/list2 > time cat /tmp/list2 | fzf-0.10.1-darwin_amd64 -fqwerty > /dev/null real 0m5.418s user 0m10.990s sys 0m1.302s > time cat /tmp/list2 | fzf-head -fqwerty > /dev/null real 0m4.862s user 0m6.619s sys 0m0.982s
2015-04-17Improvements in performance and memory usageJunegunn Choi
I profiled fzf and it turned out that it was spending significant amount of time repeatedly converting character arrays into Unicode codepoints. This commit greatly improves search performance after the initial scan by memoizing the converted results. This commit also addresses the problem of unbounded memory usage of fzf. fzf is a short-lived process that usually processes small input, so it was implemented to cache the intermediate results very aggressively with no notion of cache expiration/eviction. I still think a proper implementation of caching scheme is definitely an overkill. Instead this commit introduces limits to the maximum size (or minimum selectivity) of the intermediate results that can be cached.
2015-01-12LintJunegunn Choi
2015-01-09Reduce memory footprintJunegunn Choi
2015-01-04Remove race conditions when accessing the last chunkJunegunn Choi
2015-01-04Rewrite fzf in GoJunegunn Choi