Open NotGovernor opened 5 months ago
Might be related to the graph? I'll try deleting the metadata.json file as a temporary workaround so I can get the site back online in the meantime. It's gotten pretty big...
[edit] That worked. Site is functional again. So the pressure is off for me. :D:D Though I have only about half of the sites content up so far -- the likely size of the metadata will probably be double what it is now. (about a 1 MB file, tens of thousands of lines)
Related to issue #97 ?
yes, it seems to be the same problem. The problem is that your php enigne can't calculate the graph relations in 30 seconds. It only need to do it one time after the metadata.json has changed, after this the final html is stored in a tmp file.
So two solutions:
You only need to run this script one time after the metadata.json has changed
Thank you for the response and the python file. Might it be a good idea to remove the graph calculation from php and have a cron or something in the docker that runs the python every few minutes, processing only if the file has been modified?
I don't want to remove it completely from PHP, because if you don't have to many notes and running the non docker setup you always need then to setup a cron job, which I want to avoid. But I will think about to add a cron job to the docker image.
This is a real dead-in-the-water issue for me as I cannot shrink my site / vault. Any help would be greatly appreciated.
Describe the bug As I added more and more files to this vault over time the initial load times have climed such that recently I've started getting the following error on the console:
To Reproduce I'm not entirely sure, but it seems to be related to the quantity of files in the vault. I'm currently around 600 md's and another 600 images.
Device (please complete the following information): Client device doesnt matter. It's a server issue. Running in docker. 2 vcpu's 4 gb ram.