display current local node size on Welcome page #292

Closed
opened 2008-01-30 17:06:01 +00:00 by terrell · 2 comments
terrell commented 2008-01-30 17:06:01 +00:00
Owner

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.

[~/.tahoe] du -h | tail -1
 59M    .

I checked my node connected to the [TestGrid](wiki/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. ``` [~/.tahoe] du -h | tail -1 59M . ```
tahoe-lafs added the
code-frontend-web
major
task
0.7.0
labels 2008-01-30 17:06:01 +00:00
tahoe-lafs added this to the 0.8.0 (Allmydata 3.0 Beta) milestone 2008-01-30 17:06:01 +00:00

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.

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.
warner modified the milestone from 0.8.0 (Allmydata 3.0 Beta) to undecided 2008-01-31 01:55:48 +00:00

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.

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.
warner added the
fixed
label 2008-02-06 02:31:39 +00:00
warner modified the milestone from undecided to 0.8.0 (Allmydata 3.0 Beta) 2008-02-06 02:31:39 +00:00
Sign in to join this conversation.
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Reference: tahoe-lafs/trac-2024-07-25#292
No description provided.