Matija Šuklje
Matija Šuklje
We could still continue to roll our own, but then it needs to work. It currently doesn’t. I don’t have strong feelings one way or another which solution is better...
This issue would go away when we get rid of JQuery altogether as per https://github.com/Pelican-Elegant/elegant/issues/220
@archeranimesh It is not a priority, but it shouldn’t be hard to implement. If you look into it and produce a pull request, we would be happy to merge it.
I have 300+ posts and my server is a little ARM board, so ideal for testing bottlenecks ;) Happy to test it out :)
The results are in! Before the change: ``` Done: Processed 367 articles, 6 drafts, 2 pages and 2 hidden pages in 368.62 seconds. ``` After the change: ``` Done: Processed...
@mlissner, did you try implementing the other stuff that they mention in getpelican/pelican#1493 ?
I **really** think optimisations are a great thing to have and we should implement that. But IMHO this should not be a requirement for 2.0. If we manage to get...
Any progress here?
Fixing something like this is waaaay out of my league. I merely volunteered to test it, since I’m running Pelican on an ARM board, so any performance changes show really...
@iranzo My main concern is to make sure we have it documented what these variables do and how it affects the Tipue Search functionality.