3 ms·

Why would it be unnecessary? The amount of data follows rather logically from the amount of website state it's capturing, and the interval seems totally like pe

by gcp 10y ago

Why would it be unnecessary? The amount of data follows rather logically from the amount of website state it's capturing, and the interval seems totally like personal preference to me. Would you rather lose 60 seconds of work or 15? Uh, I'll take less data loss.

pixl97 10y ago
In a web browser? You're acting like the browser is a major local storage application (like excel for example), almost everything I'm going to be working on is an online application, and it takes care of storing my data on the server infrastructure. So yea, 15 seconds or 60 seconds isn't going to be a major 'data loss' issue either way.
- gcp 10y ago
  it takes care of storing my data on the server infrastructure Do you manually hit the save button every 15 seconds? Some webapps do this for you. Some do not. Firefox has got your ass covered even for those that do not.
- tracker1 10y ago
  You apparently haven't seen some of the SPAs that are in use out there... I can very validly consider an issue with losing even a minute vs 15 seconds being considered in favor of the latter. It might be nice if this was tunable via a setting though.
dogma1138 10y ago
what information would you lose exactly?
sliverstorm 10y ago
Why would it be unnecessary? Because you hear the data volume, the function, and you think there has GOT to be a better way
schiffern 10y ago
The problem isn't that data is being written (that's desirable, in fact). The problem imo is that data is being written unnecessarily. Firstly it shouldn't be backing up every "N" seconds. It should be backing up after every change, and for performance reasons coalescing changes in time interval bins (eg 1-5 second blocks). Secondly, it should only be writing the information that changes. Sure websites contain a lot of data, but most of it doesn't change very fast. So it's a big win to only back up the deltas (and reconstructing it is fast on SSDs). If a page does have lots of transient data... write lots of data! That's partly how the time coalescing parameter is tuned. Ideally it would only write out the entire page of data when it loads, or when the size of the deltas exceeds some threshold (possibly different for HDD vs SSD).
- db48x 10y ago
  If the data hasn't changed during the last interval, then it doesn't rewrite the file. The article mentions loading a couple of dozen pages that are probably all pinging a dozen ad servers every 15 seconds, updating their cookies and localstorage with the results, etc. It all adds up. If you really want to solve the problem, use an ad blocker, or push the pages you visit to remove the bloat.
deleted 10y ago
[deleted]

by gcp 10y ago

pixl97 10y ago

In a web browser? You're acting like the browser is a major local storage application (like excel for example), almost everything I'm going to be working on is an online application, and it takes care of storing my data on the server infrastructure. So yea, 15 seconds or 60 seconds isn't going to be a major 'data loss' issue either way.

gcp 10y ago
it takes care of storing my data on the server infrastructure Do you manually hit the save button every 15 seconds? Some webapps do this for you. Some do not. Firefox has got your ass covered even for those that do not.
tracker1 10y ago
You apparently haven't seen some of the SPAs that are in use out there... I can very validly consider an issue with losing even a minute vs 15 seconds being considered in favor of the latter. It might be nice if this was tunable via a setting though.

dogma1138 10y ago

what information would you lose exactly?

sliverstorm 10y ago

Why would it be unnecessary? Because you hear the data volume, the function, and you think there has GOT to be a better way

schiffern 10y ago

The problem isn't that data is being written (that's desirable, in fact). The problem imo is that data is being written unnecessarily. Firstly it shouldn't be backing up every "N" seconds. It should be backing up after every change, and for performance reasons coalescing changes in time interval bins (eg 1-5 second blocks). Secondly, it should only be writing the information that changes. Sure websites contain a lot of data, but most of it doesn't change very fast. So it's a big win to only back up the deltas (and reconstructing it is fast on SSDs). If a page does have lots of transient data... write lots of data! That's partly how the time coalescing parameter is tuned. Ideally it would only write out the entire page of data when it loads, or when the size of the deltas exceeds some threshold (possibly different for HDD vs SSD).

db48x 10y ago
If the data hasn't changed during the last interval, then it doesn't rewrite the file. The article mentions loading a couple of dozen pages that are probably all pinging a dozen ad servers every 15 seconds, updating their cookies and localstorage with the results, etc. It all adds up. If you really want to solve the problem, use an ad blocker, or push the pages you visit to remove the bloat.

deleted 10y ago

[deleted]