dantleech

> Why is phpactor reopening again and again the very same mapfile which could problem hold in memory? This call should be memoized, thanks: https://github.com/phpactor/phpactor/pull/2911 > Same about other files......

> I wish it could. A 30k, 12M or 126M code could hold in memory and make the thing so much responsive. Phpactor is lazy, the file accesses couild be...

> Regarding access(), they lead to ENOENT in 3667 (= 65% of the calls) on 625 distinct files. [3006 on ~/.cache/phpactor/* and 661 on actual project's files). Excerpt of the...

I get a similar total number of sycalls (8,703) for typing `Foobar` of which 1K are accesses - and it's pretty instantaenous.

I'm still not sure why you would have such severe performance issues. What spec is your machine? are you using an solid-state-drive or a HDD?

``` Run status group 0 (all jobs): READ: bw=134MiB/s (140MB/s), 134MiB/s-134MiB/s (140MB/s-140MB/s), io=100MiB (105MB), run=749-749msec ``` ``` Run status group 0 (all jobs): WRITE: bw=38.1MiB/s (40.0MB/s), 38.1MiB/s-38.1MiB/s (40.0MB/s-40.0MB/s), io=100MiB (105MB),...

yes, this is nothing to do with logging. indeed should probably be a progress message, and the same for some other progress/status-related window messages.

but at the same time -- this is the startup message - you should only see it once? is the problem rather than Phactor is being started frequently?

ok, makes sense. out of interest which editor are you using?

good to know, what is subtle for me on neovim might be intrusive in other editors or configurations 😅 in the meantime you can extend that timeout infinitely. it's basically...