MobileRead Forums - View Single Post

BeckyEbook · 04-14-2021, 03:45 PM

Ou, "double-load" or "double-pumping" are good names

I can also see them (also in the latest build).
The fact that this is so can be easily checked in Code Inspector.
Open the "Network" tab and look at the UUID at the end of the file name.
If there is a "double-pump" then it will be seen that the UUID for the same file has changed.

For example, we see the file:

Code:

sigil:///T:/TMP/Sigil-aKkZeo/epub/text/chapter-10.xhtml?sigilpreview=7c9ca741-fc4e-406e-ada7-4f815fae0d14

After "double-pump" the address changes and forces the preview window to refresh:

Code:

sigil:///T:/TMP/Sigil-aKkZeo/epub/text/chapter-10.xhtml?sigilpreview=27ad347e-09f9-4b0b-ac5d-747e77c4054a

I don't know if this will help diagnose the problem, but "something" forces a refresh and I wouldn't bet it's CSS's fault (although I may be wrong).

---

Regarding the speed tests, and the chapter files in "The Sign of the Four" ebook are too short to spot the speed problem. The differences are noticeable better when we merge all the chapters into one, because then the search for "cocaine-bottle" may take even a few seconds.

I think the reasons are known:
a) underlining misspelled words in Code View now supports two dictionaries (approx. 60% slowdown)
b) new option "Highlight Matching Tags" (approx. 40% slowdown)

When I disable both of the mentioned options 1.5.1 is fast (and the newest build is even faster).
On the other hand – with small files with chapters the slowdown even with the options turned on is slight.

My system: Windows 10 Pro (1909), I5-2500K, 16GB.

PS. Still on the possible slowdown by the antivirus program. This is certainly true, but – importantly – it's not about blocking the application, but rather adding the TEMP folder (where Sigil creates temporary files) to the threat checking exclusion list. I also prefer to note that this is not a safe solution with the TEMP location's default settings.

04-14-2021, 03:45 PM	#72
BeckyEbook Guru Posts: 809 Karma: 2416112 Join Date: Jan 2017 Location: Poland Device: Various	Ou, "double-load" or "double-pumping" are good names I can also see them (also in the latest build). The fact that this is so can be easily checked in Code Inspector. Open the "Network" tab and look at the UUID at the end of the file name. If there is a "double-pump" then it will be seen that the UUID for the same file has changed. For example, we see the file: Code: sigil:///T:/TMP/Sigil-aKkZeo/epub/text/chapter-10.xhtml?sigilpreview=7c9ca741-fc4e-406e-ada7-4f815fae0d14 After "double-pump" the address changes and forces the preview window to refresh: Code: sigil:///T:/TMP/Sigil-aKkZeo/epub/text/chapter-10.xhtml?sigilpreview=27ad347e-09f9-4b0b-ac5d-747e77c4054a I don't know if this will help diagnose the problem, but "something" forces a refresh and I wouldn't bet it's CSS's fault (although I may be wrong). --- Regarding the speed tests, and the chapter files in "The Sign of the Four" ebook are too short to spot the speed problem. The differences are noticeable better when we merge all the chapters into one, because then the search for "cocaine-bottle" may take even a few seconds. I think the reasons are known: a) underlining misspelled words in Code View now supports two dictionaries (approx. 60% slowdown) b) new option "Highlight Matching Tags" (approx. 40% slowdown) When I disable both of the mentioned options 1.5.1 is fast (and the newest build is even faster). On the other hand – with small files with chapters the slowdown even with the options turned on is slight. My system: Windows 10 Pro (1909), I5-2500K, 16GB. PS. Still on the possible slowdown by the antivirus program. This is certainly true, but – importantly – it's not about blocking the application, but rather adding the TEMP folder (where Sigil creates temporary files) to the threat checking exclusion list. I also prefer to note that this is not a safe solution with the TEMP location's default settings.