That would certainly eliminate issues with hypervisor latency.
Unfortunately, I don't have the resources to do bare metal server testing at
this point, but client is bare metal.
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting.
Knowledgeable human assistance, not telephone trees or script readers.
See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.
On Mon, 6 Apr 2015, Mike Gabriel wrote:
Date: Mon, 06 Apr 2015 20:57:23 +0000
From: Mike Gabriel <[email protected]>
To: Robert Dinse <[email protected]>
Cc: brian mullan <[email protected]>, [email protected]
Subject: Re: [X2Go-User] Jerky Video Fixed
Hi Brian, hi Robert,
On Mo 06 Apr 2015 17:39:01 CEST, Robert Dinse wrote:
I don't know enough about their cloud servers to know what else to look
at, you're giving your low latency kernel CPU cycles from a cloud, how
choppy
is the scheduling of CPU cycles to your kernel fro the cloud? Your kernel
can't schedual CPU cycles during times it doesn't have them.
I also think that testing with low latency should be from bare metal (server)
to bare metal (client).
Greets,
Mike
--
DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
fon: +49 (1520) 1976 148
GnuPG Key ID 0x25771B31
mail: [email protected], http://das-netzwerkteam.de
freeBusy:
https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb
_______________________________________________
x2go-user mailing list
[email protected]
http://lists.x2go.org/listinfo/x2go-user
