[Github-comments] [geany/geany-plugins] GeanyLua: Enable running scripts for all signals (#1112)

elextr notifications at xxxxx
Mon Oct 4 23:51:09 UTC 2021


@xiota running a test in a tight loop like that the inode _will_ be cached by Linux, and probably even by windows (although its file operations are notoriously slower than Linux) all you are testing is the cost of the allocate for the string concat and the stat system call to copy existing data, not the cost to access the file system.  This is confirmed when I run the same test on a memory filesystem, an SSD filesystem and a spinny hard disk filesystem and get the same answer.

But when the calls are not in the same closed loop the caching may not happen so well, or even not at all with some mount options.  

And for a remote file on a network (where the default is to ask for new metadata if the requests are more than 3 secs apart) there could be intermittent delays while typing.

Since the cost is incurred only when the plugin is enabled, ultimately the decision is up to the the plugin maintainer, Geany doesn't really care.



-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany-plugins/pull/1112#issuecomment-933941543
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.geany.org/pipermail/github-comments/attachments/20211004/be5b6457/attachment-0001.htm>


More information about the Github-comments mailing list