Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

If one ZIM file is "slow" then it slows down the whole Kiwix **massively** #1306

Open
kelson42 opened this issue Dec 26, 2024 · 1 comment
Open
Assignees
Milestone

Comments

@kelson42
Copy link
Collaborator

kelson42 commented Dec 26, 2024

I have wikipedia_en_all_maxi_2024-01.zim which is stored on a NAS, accessible via SMB protocol on a Ubuntu 22.04.

Even if I have a large bandwidth between my computer and my NAS, the latency is significant... at least significant enough to seriously slow down the reading experience on Kiwix.

But, even if this is an interesting point, this is not the topic of this issue. The topic is that, at from the time I have loaded this ZIM file in my local library, then everything start to be slow like:

  • Simply filtering on the local library
  • Loading an article in an other ZIM

For example, if I add a filter on my local library (with around 20 ZIM files) then it takes around 5s whereas if wikipedia_en_all_maxi_2024-01.zim is not part of the library, then it takes less than one second.

Same for loading an article which of Wiktionary (which is not stored on the NAS), it takes usually around 1s, but if I have wikipedia_en_all_maxi_2024-01.zim in the library, it takes 5s.

Considering that the two operations listed above should not require reading wikipedia_en_all_maxi_2024-01.zim, it seems to me there is a massive waste of hardware resources here.

It looks like each time the user click somewhere it implies reading wikipedia_en_all_maxi_2024-01.zim on the storage backend!?

@kelson42 kelson42 changed the title If one ZIM file is "slow" then it slows down the whole Kiwix If one ZIM file is "slow" then it slows down the whole Kiwix **massively** Dec 26, 2024
@kelson42
Copy link
Collaborator Author

It thought it might be related to monitoring of directory (ping @juuz0) but actually it seems it is not, see my configuration:
Image

@kelson42 kelson42 added this to the 2.5.0 milestone Dec 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants