2018.01.16 20:20 "Re: [Tiff] Strategies for multi-core speedups", by Kemp Watson
Actually, to follow that up, required bandwidth is pretty easy to calculate, based on your screen size, % of screen refreshed on a pan or zoom, required response time, and compression ratio.
Same for BDP limits, with packet size and packets in flight.
On Tue, Jan 16, 2018 at 3:18 PM, Kemp Watson <email@example.com> wrote:
We found that we were getting very reasonable interactivity in web browsers, with no 'fancy' WebGL, WebSockets, WebRTC, etc, just raw XMLHTTP, at about 0.5-0.6 Mbps per user. That's for viewing at screen pixel data sizes.
On Tue, Jan 16, 2018 at 3:08 PM, <Joe.Maniaci@ricoh-usa.com> wrote:
I did experiment with HTML5 + webGL in the past and I actually ran into draw call limitations by the browsers. But looking back I'm sure I did things quite incorrectly setting images up. But even then the thought did cross our minds and we basically came to the same conclusions. We may be getting some 10Gb network capabilities soon, but I'm not banking on it so I went the desktop application route.
Staff Software Engineer
From: Kemp Watson <firstname.lastname@example.org>
To: Paavo Helde <email@example.com>
Date: 01/16/2018 01:02 PM
Subject: Re: [Tiff] Strategies for multi-core speedups [EXTERNAL]
Sent by: firstname.lastname@example.org
Also Joseph, you might find yourself limited by network bandwidth or BDP long before you are limited by application threading, good idea to think about network simulation (if relevant) before detailed design.
> On Tue, Jan 16, 2018 at 2:34 PM, Paavo Helde <*email@example.com* > <firstname.lastname@example.org>> wrote:
> On 16.01.2018 20:36, *Joe.Maniaci@ricoh-usa.com*
> <Joe.Maniaci@ricoh-usa.com> wrote:
If all you want is a viewer then you are limited by the screen sizes
>> which are typically not more than ca 2000x2000 pixels. And this is pretty >> small image nowadays, there is no need to multithread anything, you could
>> just read the needed tiles from the TIFF file in real time and maybe add a >> small cache of the read tiles so you don't need to read them again if the
>> user pans left 1 pixel.
For zooming out the TIFF file should have different frames of the same image stored in decreasing resolutions so that