Browsing Abkhazian translation

615 of 111 results
6.
Doing the above on files that are laid out at different times, so as to ensure that they are fragmented and cause even more seeking.
(itstool) path: item/p
(no translation yet)
Located in C/harmful.page:23
7.
Doing the above on files that are in different directories, so as to ensure that they are in different cylinder groups and cause even more seeking.
(itstool) path: item/p
(no translation yet)
Located in C/harmful.page:28
8.
Repeatedly doing the above when it only needs to be done once.
(itstool) path: item/p
(no translation yet)
Located in C/harmful.page:33
9.
Ways in which you can optimize your code to be seek-friendly:
(itstool) path: page/p
(no translation yet)
Located in C/harmful.page:38
10.
Consolidate data into a single file.
(itstool) path: item/p
(no translation yet)
Located in C/harmful.page:43
11.
Keep data together in the same directory.
(itstool) path: item/p
(no translation yet)
Located in C/harmful.page:48
12.
Cache data so as to not need to reread constantly.
(itstool) path: item/p
(no translation yet)
Located in C/harmful.page:53
13.
Share data so as not to have to reread it from disk when each application loads.
(itstool) path: item/p
(no translation yet)
Located in C/harmful.page:58
14.
Consider caching all of the data in a single binary file that is properly aligned and can be mmapped.
(itstool) path: item/p
(no translation yet)
Located in C/harmful.page:63
15.
The trouble with disk seeks are compounded for reads, which is unfortunately what we are doing. Remember, reads are generally synchronous while writes are asynchronous. This only compounds the problem, serializing each read, and contributing to program latency.
(itstool) path: page/p
(no translation yet)
Located in C/harmful.page:68
615 of 111 results

This translation is managed by translation group gnome-translation-project.

You are not logged in. Please log in to work on translations.

No-one has contributed to this translation yet.