filesystem âlagsâ on server
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
I'm not posting this question in regards to a specific problem, but rather
something I've been continuously observing and don't understand.
When I copy files from one directory on a remote server to another, it can sometimes take a couple of second (around 10 to 20, I would estimate) for the files to "appear" in the directory it was copied to. What I mean with appear is that I don't see the file using ls
until i've waited said time. I believe this happens regardless of file size/number. The server is not "unresponsive" due to overload or too much I/O.
What could be the reason for this?
remote lag
add a comment |Â
up vote
0
down vote
favorite
I'm not posting this question in regards to a specific problem, but rather
something I've been continuously observing and don't understand.
When I copy files from one directory on a remote server to another, it can sometimes take a couple of second (around 10 to 20, I would estimate) for the files to "appear" in the directory it was copied to. What I mean with appear is that I don't see the file using ls
until i've waited said time. I believe this happens regardless of file size/number. The server is not "unresponsive" due to overload or too much I/O.
What could be the reason for this?
remote lag
caching could be the reason.
â Ipor Sircer
Nov 28 '17 at 12:43
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I'm not posting this question in regards to a specific problem, but rather
something I've been continuously observing and don't understand.
When I copy files from one directory on a remote server to another, it can sometimes take a couple of second (around 10 to 20, I would estimate) for the files to "appear" in the directory it was copied to. What I mean with appear is that I don't see the file using ls
until i've waited said time. I believe this happens regardless of file size/number. The server is not "unresponsive" due to overload or too much I/O.
What could be the reason for this?
remote lag
I'm not posting this question in regards to a specific problem, but rather
something I've been continuously observing and don't understand.
When I copy files from one directory on a remote server to another, it can sometimes take a couple of second (around 10 to 20, I would estimate) for the files to "appear" in the directory it was copied to. What I mean with appear is that I don't see the file using ls
until i've waited said time. I believe this happens regardless of file size/number. The server is not "unresponsive" due to overload or too much I/O.
What could be the reason for this?
remote lag
asked Nov 28 '17 at 12:25
PejoPhylo
1333
1333
caching could be the reason.
â Ipor Sircer
Nov 28 '17 at 12:43
add a comment |Â
caching could be the reason.
â Ipor Sircer
Nov 28 '17 at 12:43
caching could be the reason.
â Ipor Sircer
Nov 28 '17 at 12:43
caching could be the reason.
â Ipor Sircer
Nov 28 '17 at 12:43
add a comment |Â
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f407492%2ffilesystem-lags-on-server%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
caching could be the reason.
â Ipor Sircer
Nov 28 '17 at 12:43