Hi all,

I'm curious, is there an explanation anywhere of what the ranges are for RemoteCompression and RemoteReadSize, and what the values mean?

For example, if I set RemoteCompression to 5 what does the 5 actually mean?  Is it 5% out of 100?

It would be nice to know what the values are based on instead of just blindly assigning numbers.

Thanks.

= Steve

On 2/18/2016 10:33 PM, Steve Gill wrote:
> I'm curious, is there an explanation anywhere of what the ranges are for RemoteCompression and RemoteReadSize, and what the values mean?

RemoteReadSize :
http://www.elevatesoft.com/manual?action=viewprop&id=edb2&product=rsdelphiwin32&version=10S&comp=TEDBDataSet&prop=RemoteReadSize

It's simply how many rows should be returned for remote session
requesting data. You're basically doing bulk reading/paging and over
slower network links increasing this can really pay off (since you're
getting hit with latency only once instead of once per row read).

It can also slow things down so you should run some tests based on your
own data. If you only need 1 row then this will not help; however if
you're going thru the table sequentially it can speed things up a lot we
found.

> For example, if I set RemoteCompression to 5 what does the 5 actually mean?  Is it 5% out of 100?

RemoteCompression  is here :
http://www.elevatesoft.com/manual?action=viewprop&id=edb2&product=rsdelphiwin32&version=10S&comp=TEDBSession&prop=RemoteCompression

It's a compression value between 0 (none) and 9.

AFAIk EDB uses ZLib so these are standard compression levels for ZLib as
well (if you were to google it).

Basically 0 is none, 9 is max compression. 1 would be best speed, 3 and
6 are considered good compromises (6 is default).

if you're running over a slow link (slow internet these) and sending lot
of data then additional compression might be worthwhile - however you
should test.

I know we did some benchmarks long time ago with DBISAM and on fast LAN
the 3 and 6 ended up being best options for us with out data (we stayed
with 6 since the 3 was not significantly better and in some cases 6 won).

Raul

Thanks Raul.  Silly me, I was looking in the wrong manual (the SQL manual instead of the other one).

Thanks for your suggestions too.

= Steve

Steve,

Raul covered this pretty well, but I'd just like to add this bit:

When it comes to grids or other multi-line controls, EDB will *automatically* set the RemoteReadSize temporarily so that it matches the number of visible rows in the grid.  This makes populating a grid much faster because the remote session will grab the exact number of rows that it needs only once.

Tim Young
Elevate Software
www.elevatesoft.com

Hi Tim,

<< When it comes to grids or other multi-line controls, EDB will *automatically* set the RemoteReadSize temporarily so that it matches the number of visible rows in the grid.  This makes populating a grid much faster because the remote session will grab the exact number of rows that it needs only once.  >>

Thanks for that. The only problem is I'm not using data-aware grids because my customers hate the 3-position scroll bars.  So I wrote some classes that are responsible for managing the grids (loading, updating, refreshing, deleting records, showing status icons, and so on).

= Steve