I tried setting these properties first to 6250 and later both to 100.
Neither setting appeared to have any significant impact. (And, yes, I
did get rid of the "#" in column 1)  :-)

I am using the December 7th nightly build to try out this capability.

I tried first via VPN, then directly to the site. No impact of setting
these parameters in either configuration.

Any ideas? 

-----Original Message-----
From: Christensen, Alan 
Sent: Thursday, December 08, 2005 8:45 AM
To: JMeter Users List
Subject: RE: Testing the effect of page compression with Jmeter; Any
gotchas?

The only lines that I could find in the Dec 7th nightly build regarding
this property are in the Jmeter properties file:

# Define characters per second > 0 to emulate slow connections
#httpclient.socket.http.cps=0 #httpclient.socket.https.cps=0

I just want to confirm that I should be using 8 bits/character. My
suspicion is also that a 50kbps line doesn't really deliver 6250
char/sec but some smaller number due to overhead.  Is this the case?  If
so, should I use a smaller number for "httpclient.socket.http.cps" than
6250?  If anyone has thoughts on the most appropriate number to use to
simulate a 50kbps dialup line, then I'd appreciate their advice.

-----Original Message-----
From: Peter Lin [mailto:woolfel@gmail.com]
Sent: Thursday, December 08, 2005 8:19 AM
To: JMeter Users List
Subject: Re: Testing the effect of page compression with Jmeter; Any
gotchas?

sebb would know how to do that. I believe he updated the docs in SVN,
but the website hasn't been updated yet. if you download a nightly, the
docs packaged in the tar/zip should have an explanation.

peter


On 12/8/05, Christensen, Alan <alan.christensen@hp.com> wrote:
>
> How exactly is this property set for various speeds? If I wanted to 
> emulate a 50kbps dialup line, what would I set this property to?  Do I

> set it to 50000/8 = 6250?
>
> -----Original Message-----
> From: sebb [mailto:sebbaz@gmail.com]
> Sent: Monday, November 28, 2005 9:02 AM
> To: JMeter Users List
> Subject: Re: Testing the effect of page compression with Jmeter; Any 
> gotchas?
>
> As to slower connections, the latest nightly builds include a means of

> simulating slow connections for the Apache HttpClient sampler.
>
> See jmeter.properties:
>
> #httpclient.socket.http.cps=0
> #httpclient.socket.https.cps=0
>
> ==
>
> I looked at extending this to the default Http implementation, but it 
> is non-trivial, and requires overriding the boot classpath, as one has

> to create a java.net class.
>
> S.
> On 28/11/05, Christensen, Alan <alan.christensen@hp.com> wrote:
> >
> > Has anyone used Jmeter to test the effects of using page compression

> > vs not using page compression?  Any gotchas that should be avoided, 
> > or
>
> > best practices that will make this easier?  What would you suggest 
> > be used to mimic slower connections?
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org