login::
pass::
name::
id::
node:
Re[3]: 30.03.2011-20:18:35
template:
4
parent:
Re[2]: 30.03.2011-20:18:35
owner:
Trilobite
viewed by:
created:
31.03.2011 - 10:34:51
cwbe coordinatez
:
101
63540
63542
2109677
1857521
5920312
5920413
5921014
5921240
ABSOLUT
K
YBERIA
permissions
you:
r,
system:
public
net:
yes
так
neurons
stats
|
by_visit
|
by_K
source
tiamat
K
|
my_K
|
given_K
last
commanders
polls
total descendants::2
total children::1
show[
2
|
3
]
flat
ale to by zatazovalo procak lokalne, nie na NAS
title/content
title
content
user
00000101000635400006354202109677018575210592031205920413059210140592124005921263
maniac
31.03.2011 - 10:43:17
, level: 1,
UP
NEW
Re[4]: 30.03.2011-20:18:35
zalezi od IO vykonu NASu
totiz tie nahlady vyzaduju vela seekovania a ked ma NAS seekovat vo velkom mnozstve dat vo vela suboroch tak to spravi vela hw interruptov a tym padom cpu bude dlho cakat na dokoncenie diskovych operacii takze pri sledovani zataze sa to tvari ako vytazene cpu systemovymi (kernel, resp wait states) operaciami
0000010100063540000635420210967701857521059203120592041305921014059212400592126305921322
Trilobite
31.03.2011 - 11:00:26
, level: 2,
UP
NEW
Re[5]: 30.03.2011-20:18:35
ach so.