Version: v1.101.3 Operating System: Ubuntu Environment: Docker It seems that the new feature “save-state-resume GC filewalker” isn’t functioning as expected. Both new databases (used_space_per_prefix.db and garbage_collection_filewalker_progress.db ) always remain empty (no records with satellite…

Cache isn’t just used once, it’s used every time the file(metadata) is needed. That could be every time the GCs run for example. There is no point in caching pieces for customers. Resources are better spent on caching information about the millions of pieces that the node is storing, speeding up an…

[image] Mitsos: Cache isn’t just used once, it’s used every time the file(metadata) is needed. That could be every time the GCs run for example. Right, I forgot about the other filewalkers. [image] Mitsos: There is no point in caching pieces for customers. What vfs_cache_pressure valu…

[image] jammerdan: What vfs_cache_pressure value do you suggest? I don’t change it for my systems.

[image] Mitsos: I don’t change it for my systems. Neither me, but without changing, I surprised that Linux did exactly what I wish: Having lot’s of unused memory: [image] And significant part of the cache (yellow lines) spent to cache the inodes (ext4_inode_cache): [image] (first is fr…

When in htop: press F2 (setup) > down arrow to meters > right arrow until you get to memory > press space. it should be like this: [Screenshot_20240612_215737] This is the result: [Screenshot_20240612_215808] Edit: because discourse is doing its thing where replied-to gets evaporated into thin a…

[image] elek: I totally agree with you, we need this feature, I see things are going to be discussed: Storage node performance for filewalker is still extremely slow on large nodes · Issue #6998 · storj/storj · GitHub Please do not delay this feature any further even if you might agree on ot…

[image] elek: but won’t solve fully the problem Here is one problem I have now as I had to turn off the regular filewalker: [image] Overriding available space? troubleshooting I had to disable the filewalker on this node as it would not finish. Now of course the u…

[image] elek: The problem with filewalkers is retrieving the size and last modification time. With ext4 file system, directory entries contain only the file names. An additional read of the inode is required for getting the size and last modification time of the files. What if we add that to …

[image] jammerdan: Something like piecename.sj1.year-month-day e.g.: Taking a random piece from one of my nodes: xwx3njdry2vhdthddq23773yfwcm4tv73qdpv65o7topw3pepq.sj1.2024-02-07. Then you make downloads much slower. You can’t “just” open a file, you have to scan the whole subdirectory each t…

[image] jammerdan: What vfs_cache_pressure value do you suggest? I’m experimenting with vfs_cache_pressure=1 on one of my hosts. After leaving it overnight, almost all RAM reported as buffers was converted into cache. slabtop shows dentry as first sorted so there’s that. Edit: had a memory p…

Storj Community Forum (official)

It seems that the new feature “save-state-resume GC filewalker” isn’t functioning as expected

Node Operators troubleshooting