* Juiceman <juiceman69 at gmail.com> [2007-05-11 19:59:13]: > > > >No, I don't have data and/or references. As you said yourself "the > >50%-50% limit is arbitrary". Why did you decide on 50%, where is > >your statical results from a simulation? What I do know is my gut > >tells me I probably have one the largest caches in Freenet. Any > >request that passes thru my node has a good chance of finding the data > >in my node. Hence, my outbound bandwidth is always pegged at 25KB/sec > >(which I don't have a problem with) I just have a feeling the "deep > >store of data" that I want my node to concentrate on is not being > >served because its answering "random requests." Is there a histogram > >of inbound and outbound transfers somewhere I can check? > > > >BTW, I recently "nuked" my datastore so I would stop seeing error > >messages about my store and corruption (and I knew it would fill back > >up quick enough with random requests). Maybe we should hide error > >messages from users so they think everything is "peachy"? > > > > What if I make a check that the store can never be smaller than the > cache? Would that alleviate your concerns? It would reduce > functionality while still giving me the option.
Fine but if I understood correctly what you want to do, it defeats the purpose. > > Oh, I also forgot to say when you decide you want to experiment with > the ratio of the cache to store in the future, because you will > someday you will just have to create the code anyways. So what's the > harm in letting those of us who use the "expert settings" try this? > > Maybe we need a third level of settings "Developer" for all the > settings that have the comment "Leave this alone". Why do we even > include them? Developers can "maintain their own fork" (in your > words) Convenience. > > Here is a list of options that even "experts" shouldn't touch, by your > reasoning: (My comments in quotes > > TMCI section "This has no relevence to anyone other than a *nix geek > or a developer." > > # Override the CSS with a custom one (WARNING!)That setting allows you > to override the node's CSS with a custom file. WARNING: CSSes can be > dangerous and won't be filtered! use at your own risks. (consider > mailing devl at freenetproject to get it included in the main > distribution ;) ) > > Disable probabilistic HTL (don't touch this unless you know what you are > doing) > > Maximum HTL (FOR DEVELOPER USE ONLY!) > > Frequency of dropping packets. Testing option used by devs to simulate > packet loss. 0 means never artificially drop a packet. Don't touch > this! > > Interval between swap attempting to send swap requests in > milliseconds. Leave this alone! > > Disable all hang checkers/watchdog functions. Set this if you are > profiling Fred. > > Disable all hang checkers/watchdog functions. Set this if you are > profiling Fred. > > Enables the user to tweak the time in between GC and forced > finalization. SHOULD NOT BE CHANGED unless you know what you're doing! > -1 means: disable forced call to System.gc() and > System.runFinalization() > > node.scheduler section > > Whether to enable testnet mode (DANGEROUS!). Testnet mode eliminates > your anonymity in exchange for greatly assisting the developers in > debugging the node. > > > > Now, why is my proposed change any worse than these? Those have local effects... what you propose to introduce can have network-wide effects. I'm not sure it's worst, but in any case it's yetAnotherOne. NextGen$ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Digital signature URL: <https://emu.freenetproject.org/pipermail/tech/attachments/20070512/fd7b2d0f/attachment.pgp>
