From: "Sivaraman Nainar" <sivaramann@amiindia.co.in>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
"maciej.rabeda@intel.com" <maciej.rabeda@intel.com>
Subject: Re: [edk2-devel] reg: reg : HTTP Download Performance
Date: Fri, 3 May 2019 05:23:20 +0000 [thread overview]
Message-ID: <B4DE137BDB63634BAC03BD9DE765F1970242F59C2E@Venus2.in.megatrends.com> (raw)
In-Reply-To: <40FBBD5C52E8B4429773266A45BDCC174C5BFE66@IRSMSX104.ger.corp.intel.com>
[-- Attachment #1: Type: text/plain, Size: 2913 bytes --]
Hi Maciej Rabeda:
Its Mb/s only.
Shall we have ticket to track this.
-Siva
From: devel@edk2.groups.io [mailto:devel@edk2.groups.io] On Behalf Of Rabeda, Maciej
Sent: Thursday, April 25, 2019 3:29 PM
To: devel@edk2.groups.io; Sivaraman Nainar
Subject: Re: [edk2-devel] reg: reg : HTTP Download Performance
Hi Siva,
Summary:
UEFI HTTP: 2.35 Mbps
Windows wget: 14.1 Mbps
Could you clarify whether in the LAN scenario you get 100 Megabytes or Megabits per second?
If you are getting 100 MB/s (instead of 100 Mb/s), I would like to follow up on how did you achieve such speeds :)
If it's 100 Mbps, this sounds to be pretty slow for current UEFI network stack, knowing it can do ~550 Mbps when doing PXE boot with WDS server set on LAN (so network stack up to UDP seems to be working at least this fast). In case of HTTP boot, there is TcpDxe <-> HttpDxe <-> HttpBootDxe path that would have to be checked for bottlenecks.
Thanks!
Maciej Rabeda
DCG CG ND SW ITP PreBoot Dev
From: devel@edk2.groups.io<mailto:devel@edk2.groups.io> [mailto:devel@edk2.groups.io] On Behalf Of Sivaraman Nainar
Sent: Wednesday, April 24, 2019 12:36
To: devel@edk2.groups.io<mailto:devel@edk2.groups.io>
Subject: [edk2-devel] reg: reg : HTTP Download Performance
Hello All:
Would like to clarify few information on the timings on the HTTP Boot / Download performed through Windows / Linux and UEFI HTTP Boot.
There was a HTTP server running in California and when an 450 MB ISO tried to downloaded from that below are the time took to download. The data retroeived with the same Platform and same controller.
UEFI HTTP:
1529 seconds
310128 Bytes/seconds
Windows wget:
255 seconds
1859551 Bytes/seconds
The performance is still high (over 100MB/s) if the server is in LAN.
When we tried to change MNP_SYS_POLL_INTERVAL from (10 * TICKS_PER_MS) to (5 * TICKS_PER_MS) it does not give big change in download time.
Is there any other way to increase the speed or its limitation due to the single threaded execution.
-Siva
---------------------------------------------------------------------
Intel Technology Poland sp. z o.o.
ul. Słowackiego 173 | 80-298 Gdańsk | Sąd Rejonowy Gdańsk Północ | VII Wydział Gospodarczy Krajowego Rejestru Sądowego - KRS 101882 | NIP 957-07-52-316 | Kapitał zakładowy 200.000 PLN.
Ta wiadomość wraz z załącznikami jest przeznaczona dla określonego adresata i może zawierać informacje poufne. W razie przypadkowego otrzymania tej wiadomości, prosimy o powiadomienie nadawcy oraz trwałe jej usunięcie; jakiekolwiek przeglądanie lub rozpowszechnianie jest zabronione.
This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). If you are not the intended recipient, please contact the sender and delete all copies; any review or distribution by others is strictly prohibited.
[-- Attachment #2: Type: text/html, Size: 8914 bytes --]
prev parent reply other threads:[~2019-05-03 5:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-24 10:35 reg: reg : HTTP Download Performance Sivaraman Nainar
2019-04-25 9:59 ` Rabeda, Maciej
2019-05-03 5:23 ` Sivaraman Nainar [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=B4DE137BDB63634BAC03BD9DE765F1970242F59C2E@Venus2.in.megatrends.com \
--to=devel@edk2.groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox