[haiku-bugs] Re: [Haiku] #8007: [app_server] fully unresponsive when resizing window of big textfile
- From: "Haiku" <trac@xxxxxxxxxxxx>
- Date: Thu, 11 Oct 2012 10:02:18 -0000
#8007: [app_server] fully unresponsive when resizing window of big textfile
-----------------------------+----------------------------
Reporter: ttcoder | Owner: axeld
Type: bug | Status: new
Priority: normal | Milestone: R1
Component: System/Kernel | Version: R1/Development
Resolution: | Keywords:
Blocked By: | Blocking: 7882, 8136
Has a Patch: 0 | Platform: All
-----------------------------+----------------------------
Comment (by bonefish):
Replying to [comment:66 jua]:
[...]
> Most relevant are cases (3) and (4), the sys time increases ~8% in (3)
and ~10% in (4), but for the real time it looks much less bad. Note that I
only ran these builds one time each, so there is certainly an error
margin, especially because the build process downloads files... I didn't
set up a caching proxy or anything, so internet download speed fluctuation
is in there too. That probably decreases the significance of the real time
values.
The test procedure I used to use when testing optimizations is the
following:
1. Build an image.
1. Remove the image and the objects, but keep the downloads, so they
won't be downloaded again during the test. I don't think that the download
part is significant for the test. I think it mostly adds useless wait
times.
1. Reboot.
1. First test (cold): Build the image.
1. Remove image and objects.
1. Second test (warm): Build the image.
The second test is the more interesting one, since it reduces I/O wait
times, thus increasing the pressure on the relevant code paths. A short
version of the test could be to just build the kernel, not the complete
image.
I'd like to test on my Core i7 with 8 jobs -- which should be even more
interesting -- but I don't know when I'll get to do it.
--
Ticket URL: <http://dev.haiku-os.org/ticket/8007#comment:69>
Haiku <http://dev.haiku-os.org>
Haiku - the operating system.
Other related posts:
