A Small Optimization for File Directory Mapping #1259
Replies: 9 comments 20 replies
|
ok, it will be included in the next release. |
|
indeed, @ is working fine in my tests. |
|
from what you say, it seems that it's a problem related to your plugin. |
|
wait, in your video you were showing that only sharp and thumbnails were active, and it crashed. right? |
|
admin > logs > options > "debug messages in console" enable this to get potentially more info |
|
i'm now reproducing the problem. |
|
it seems to happen only on Windows, and not on my mac. |
|
it seems that the problem is a regression of 3.3.0-beta2 – i'm working to fix it. |
|
cool! published beta3. |
Uh oh!
There was an error while loading. Please reload this page.
A Small Optimization for File Directory Mapping:
Could an option be added to "defer" or "lazy-load" a folder?
Here is the scenario: For example, the root directory of the home page or a certain directory mounts multiple folders from hard drives A, B, C, D, E, F, G. Once you enter the home page, it triggers all the hard drives to spin up simultaneously, which causes server lag and increases the risk of unstable current draw for the drives.
Since these are mapped file directories, it would be feasible to add a checkbox option in the settings panel for these "Shared files" folders, labeled something like "Persistent Mount" or "Lazy Mount." This way, when accessing the home page, not all dormant hard drives would be awakened at the same time. Instead, the corresponding hard drive would only spin up when you actually enter that specific folder.
All reactions