@isVeryLoud It was for me, I monitored the server and each query would bump up the memory quite a bit. But that sucker had only 512 MB I think. It could’ve been some issue that’s already fixed with newer Searx versions.
Tech, FOSS, Linux and more!
@isVeryLoud It was for me, I monitored the server and each query would bump up the memory quite a bit. But that sucker had only 512 MB I think. It could’ve been some issue that’s already fixed with newer Searx versions.
@dan I see, what’s the problam with Brendan Eich, is he the former Firefox CEO?
@isVeryLoud @hash0772 I had similar experience. I was able to resolve the slowness by enabling swap on the vps. What was worst is that over time Bing and Google API changed and it stopped working, took quite long troubleshooting. Occasionaly I would hit some kind of rate limit and got nothing from Google. It was too much hassle and not worth the vps cost.
@KarnaSubarna Great news! Next step is improving the menu, adding more options and Firefox will be usable again!
@neme They should organize the menus in one place and add more overall customization options instead. Seems they just randomly jump in different directions ignoring their core users.