sebastian.rot...@jpberlin.de wrote:
On Fri, Apr 24, 2009 at 6:12 PM, <sebastian.rot...@jpberlin.de> wrote:
If you've serval houndret GBs that gonna take a loooong time.
Also you can not restore a backup quickly because of the uberproor write
performance (it feels like being slower then PIO 3..).
crypto is slow. what else is new?
I do not talk about a P2 266Mhz System here nor do I think that a loss of
even 20% write performence is "slow" anyway but a write speed of like
1-3MB/s on a modern SATA HDD on a IBM Thinkpad x61s can't be it.
The "bug" was introduced somehow between 4.1 and 4.2 (my guess).
svnd worked normaly before.
One suggestion that would may be taken more seriously if what you say is
true would be to actually go back in time and do binary search of VCS
changes to show, "Here diff 1.xxx on what ever date was fas, then with
that diff, new results" and that will give you something to work with
and that may be then someone might look into it.
That's hard evidence and that actually would/could be useful.
That approached takes times, "your time" and would actually be much more
productive if you actually believe it's a bug and if you actually would
like it to be solved, again assuming there is a new bug.
I do this time to time when I try to track something that changed and
that affected, or could have affected something else and when you
provide the results like that, you have much more change to be taken
seriously oppose to be ignore as you provide nothing here more then
compare OpenBSD with some other OS and you will only get a legit reply
as to go use that other OS then if that's what you are after.
Now you th9nk this bug (if any here) was introduce between 4.1 and 4.2.
Well, all the changes are in CVS and if you can pin point it and show it
to be real, then you will have the attention of someone that will look
into it IF you can prove your point and show the diff that introduce
what you think is a bug.
Just my $0.02 worth if you actually want to be productive at it and best
yet, be consider as a bug and get fix, if that's the case obviously.
Without hard proof, you will not get or convince anyone to even look
into it.
Hope this help you some.
Best,
Daniel
