Subject: NDT-DEV email list created
- From: Jacques Latour <>
- To: Aaron Brown <>, Jordan McCarthy <>, "" <>
- Cc: Stuart Olmstead-Wilcox <>, Xiaoping Jie <>, Tongfeng Zhang <>, "Mike Niyonkuru" <>, Don Slaunwhite <>, Cari Soutar <>
- Subject: [ndt-dev] NDT 3.7.0 final pre-release questions
- Date: Thu, 30 Apr 2015 03:02:41 +0000
- Accept-language: en-US, en-CA
As some of you may know, .ca (CIRA) is planning to publicly launch our Internet Performance Test site (http://cira.ca/performance and http://performance.cira.ca) next week, it's based on the Flash NDT client, we're using the latest and greatest. We're really excited!!
Right now, we're in beta testing until May 5.
One thing that's bugging me is that we get different performance results based on different buffer size and browsers in a controlled environment. It seems that we would get better performance results if the flash client uses a bigger buffer, 32K seems to work everywhere, 48K likely candidate for us, and 64K seems to be correct but crashes in Chrome sometimes. (what's the science behind this number?)
The second thing, the data in the buffer runs from 00 --> FF, so repetitive and compressible (if that's a word :), is that a problem?
So, by reading the C2S spec, it says the following; "must use 8K buffer" but other than with the java client, we get better results for larger buffer size. See table below and attached document for results.
What about this known limitation? Can we run 15 seconds?
Let me know what you think, any insight, wisdom, assistance would be appreciated!
NDT Testing Buffer Size.docx
Description: NDT Testing Buffer Size.docx
- [ndt-dev] NDT 3.7.0 final pre-release questions, Jacques Latour, 04/30/2015
Archive powered by MHonArc 2.6.16.