display current local node size on Welcome page #292
Labels
No Label
0.2.0
0.3.0
0.4.0
0.5.0
0.5.1
0.6.0
0.6.1
0.7.0
0.8.0
0.9.0
1.0.0
1.1.0
1.10.0
1.10.1
1.10.2
1.10a2
1.11.0
1.12.0
1.12.1
1.13.0
1.14.0
1.15.0
1.15.1
1.2.0
1.3.0
1.4.1
1.5.0
1.6.0
1.6.1
1.7.0
1.7.1
1.7β
1.8.0
1.8.1
1.8.2
1.8.3
1.8β
1.9.0
1.9.0-s3branch
1.9.0a1
1.9.0a2
1.9.0b1
1.9.1
1.9.2
1.9.2a1
LeastAuthority.com automation
blocker
cannot reproduce
cloud-branch
code
code-dirnodes
code-encoding
code-frontend
code-frontend-cli
code-frontend-ftp-sftp
code-frontend-magic-folder
code-frontend-web
code-mutable
code-network
code-nodeadmin
code-peerselection
code-storage
contrib
critical
defect
dev-infrastructure
documentation
duplicate
enhancement
fixed
invalid
major
minor
n/a
normal
operational
packaging
somebody else's problem
supercritical
task
trivial
unknown
was already fixed
website
wontfix
worksforme
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Reference: tahoe-lafs/trac-2024-07-25#292
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I checked my node connected to the TestGrid and found 59M. While not totally a surprise, I would like to see that reported (tracked over time?) on the Welcome page of my node.
Overview/Dashboard data is always good to make visible.
Funny, at first I thought you mean RAM footprint, and I was thinking "59M,
wow, that's kind of big". Then I noticed that you're talking about disk
footprint, and I thought "59M, wow, that's really small" :-).
I assume that you didn't set sizelimit to '0', since we haven't really made
it easy or obvious to do that, so you're probably picking up shares from
everyone else who connects to the test grid. If you poke inside your node's
basedir, you ought to find that almost all of that 59MB is coming from the
storage/shares/ directory.
The only immediate concern I'd have with implementing this display is that
the 'du' command will take a long time to run once the storage directory gets
very large, so I'd be nervous about running it all the time. (also, there are
cross-platform compatibilty issues to resolve). On the other hand, the
storage server class tries to keep track of how much space is being consumed,
updated incrementally, so it would probably be relatively cheap to display
that value on the welcome page. The remaining question is how to cleanly get
the data from the storage server to the web server.. we probably need some
internal cleanup for that.
I've added this display, in changeset:27f46f2aaf5479b0. The code uses
StorageServer.allocated_size()
, which combines how much space is currently used on disk with the space that has been allocated (but not yet filled) by incoming allocate-share requests. The display is just raw bytes right now, so it's kind of ugly. I'd be happy to accept a patch that formats is slightly better, the code is in src/allmydata/webish.py Root:data_storage(), around line 1319.