3 ms·
> but it's just way too slow with large history files hey! what issues were you having here? slow to open or slow to search? we have a whole bunch of people w
by ellieh 3y ago
> but it's just way too slow with large history files
hey! what issues were you having here? slow to open or slow to search?
we have a whole bunch of people with way more than 170k lines, so that shouldn't be happening :/
- bobbob1921 3y agoI’m self hosting my ATUIN server (although it is offsite so about 50 ms away), and have right at 100,000 items as shown by the command atuin status I don’t have any speed or lag issues, it comes up instantly and searches instantly. Fwiw. I Love the project (will donate now, I remember when the project wasn’t taking donations, and I suggested they should) Thanks Edit: I should add: I have the client on about 15 to 20 different VM‘s, all with various OSes and versions. The server part I’m running w docker (I think, via the exact steps suggested in the docs). All Works great in my use case, and I do have some very long and complex commands that it’s storing
- lanza 3y agoThe delay between the physical keystroke and rendered text insertion + search filtering is uncomfortably high. Compared to FZF's instantaneous rendering of the same this is a UX downgrade.