Discussion:
esnipe - how much buffer time?
(too old to reply)
PDX_Pinball
2005-05-14 16:04:53 UTC
Permalink
I'm using esnipe for the first time and want to see what kind of buffer
time everyone uses. The default is 6 seconds, but not sure how close I
can cut it. Suggestions?
JDubbbs
2005-05-14 16:07:56 UTC
Permalink
I had mine set for 3 seconds.. dont leave much time for someone else to
do the same

John
jdubbbs
John Wart, jr
2005-05-14 16:09:36 UTC
Permalink
I've used 3 seconds as well, but have had an occasion where that was too
long, somehow latency in the internet caused my bid to not be placed.

4-6 seconds is safer. I've not tried less than 3, but it could be fun.

I still prefer to manually snipe, but I don't wait up til 3 AM anymore :)
--
http://www.myhomegameroom.com
Post by JDubbbs
I had mine set for 3 seconds.. dont leave much time for someone else to
do the same
John
jdubbbs
guinness
2005-05-14 16:42:04 UTC
Permalink
Post by JDubbbs
dont leave much time for someone else to do the same
The time it takes to refresh at 6 seconds, notice someone else bid, then
outbid is impossible. It doesn't matter if you do 6 secs or 3 secs....at
that point you are only bidding against other pre-set snipers.

tim (NH)
Post by JDubbbs
I had mine set for 3 seconds.. dont leave much time for someone else to
do the same
John
jdubbbs
Ben
2005-05-14 16:58:48 UTC
Permalink
On Sat, 14 May 2005 12:42:04 -0400, "guinness"
Post by guinness
dont leave much time for someone else to do the same
The time it takes to refresh at 6 seconds, notice someone else bid, then
outbid is impossible. It doesn't matter if you do 6 secs or 3 secs....at
that point you are only bidding against other pre-set snipers.
Exactly. I use 6 seconds all the time, no problems so far out of 50+
snipes.
Jim D.
2005-05-14 19:50:51 UTC
Permalink
This post might be inappropriate. Click to display it.
henri
2005-05-14 22:27:22 UTC
Permalink
Post by Jim D.
Not necessarily true. The trick is to have one window monitoring the bidding
and another with a bid ready to confirm. You can do this easily in the last
6 seconds IF network response time & eBay response time is good. Don't try
it at 9PM EST on a Sunday but then automated sniping tools may fail also,
Some good ones have adaptive bid times. They moitor bid response times
frequently and adapt the bid lead times accordingly.
I haven't found any automated snipe service or software to be totally
dependable. What happens if esnipe needs to place 1000 bids all at 3
seconds to some specific time. Unless it has 1000 different connections to
the Intenet, they can't be placed simultaneously.
while no software will be totally dependable (i've never used esnipe or
others), i'm not sure you get how internet "connections" work....

there is no limit to how many concurrent requests your computer can make

well, there is, and it is set by the operating system and how much
memory/cpu/resources you have available at that moment in time - and it's
more than 1000, closer to 32,000 on a standard unix machine)

think about when you load the front page of ebay: you are in fact making a
request for each image on the page and you are making all those requests
at the same time, yet you only have "one internet connection".

henri
Jim D.
2005-05-15 18:42:07 UTC
Permalink
Although I have been working with computers for 40 years, there's definitely
a lot I don't know. When people start talking about pipelining, persistent
connections and transport compression, my eyes glaze over. However, one
thing has not changed in 40 years. You can't put 10 lbs of manure in a 5
pound bag. Yes, you can initiate a single request that causes many links to
be loaded but the subsequent events do not occur simultaneously. Events can
occur in very quick succession, of course. When you load a page, the viewer
is making a single request but a series of requests usually go off after the
initial request to gather, execute, and/or display all the components. You
can see this when you load a page with a lot of images on a slow connection.
Neither the links nor the displays are executed simultaneously but
sequentially as the process is ultimately limited by the communications
protocol.

Unfortunately, if you want to get into a discussion of the relationship of
HTTP and PPP & HDLC over TCP/IP, I'm not your man. I long ago reached my
level of incompetency and now I just have to sound sagacious and throw out a
few acronyms & buzz words.
Post by henri
think about when you load the front page of ebay
And think about when you try to load the front page of eBay into two
different browser windows simultaneously.

Jim D..
Post by henri
Post by Jim D.
Not necessarily true. The trick is to have one window monitoring the bidding
and another with a bid ready to confirm. You can do this easily in the last
6 seconds IF network response time & eBay response time is good. Don't try
it at 9PM EST on a Sunday but then automated sniping tools may fail also,
Some good ones have adaptive bid times. They moitor bid response times
frequently and adapt the bid lead times accordingly.
I haven't found any automated snipe service or software to be totally
dependable. What happens if esnipe needs to place 1000 bids all at 3
seconds to some specific time. Unless it has 1000 different connections to
the Intenet, they can't be placed simultaneously.
while no software will be totally dependable (i've never used esnipe or
others), i'm not sure you get how internet "connections" work....
there is no limit to how many concurrent requests your computer can make
well, there is, and it is set by the operating system and how much
memory/cpu/resources you have available at that moment in time - and it's
more than 1000, closer to 32,000 on a standard unix machine)
think about when you load the front page of ebay: you are in fact making a
request for each image on the page and you are making all those requests
at the same time, yet you only have "one internet connection".
henri
henri
2005-05-15 19:35:02 UTC
Permalink
This post might be inappropriate. Click to display it.
Jim D.
2005-05-15 21:55:08 UTC
Permalink
I get the feeling you're talking about CPU requests and I'm talking about
application requests. Different animals. No question a CPU can process
millions of instructions per second. Even billions nowadays. And, high
speed Intenet connections pass The bottleneck isn't processor speed. It's
the size of the pipe, the efficiency of the communications protocol, and the
ability of the receiving party to process the request once it receives it. I
guarantee you that come Sunday evening eBay's ability to process is
diminished by the sheer volume of messages. Not as bad as it used to be as
when they were growing faster than they could install hardware but
noticeable nonetheless.

Where are the communications engineers when you need one? I'm no computer
scientist, but somebody please explain to me what happens when a message is
sent via an application protocol like HTTP over TCP/IP over a T-1 or cable
modem and how fast such messages can be successfully exchanged.

Jim D.
Post by henri
i'm sorry, but all the REQUESTS _do_ occur simultaneously (for all
intents and purpose, i'm sure they don't happen within the same cpu
instruction, but at XXXmhz it happens so quickly that it basically is
simultaneous).
your example shows that with a slow connection the RESPONSES do not
complete simultaneously. not the same thing.
esnipe doesn't really care about the response (well, they do, but it is
not time critical)
so from the point of view of esnipe and ebay there is no real limit to
how many people they can have bid on the same auction with only 3 seconds
to go (like i said earlier, the limit _might_ be around 32K per computer
esnipe is using to send bids to ebay)
henri
Post by Jim D.
Although I have been working with computers for 40 years, there's definitely
a lot I don't know. When people start talking about pipelining, persistent
connections and transport compression, my eyes glaze over. However, one
thing has not changed in 40 years. You can't put 10 lbs of manure in a 5
pound bag. Yes, you can initiate a single request that causes many links to
be loaded but the subsequent events do not occur simultaneously. Events can
occur in very quick succession, of course. When you load a page, the viewer
is making a single request but a series of requests usually go off after the
initial request to gather, execute, and/or display all the components.
You
Post by henri
Post by Jim D.
can see this when you load a page with a lot of images on a slow connection.
Neither the links nor the displays are executed simultaneously but
sequentially as the process is ultimately limited by the communications
protocol.
Unfortunately, if you want to get into a discussion of the relationship of
HTTP and PPP & HDLC over TCP/IP, I'm not your man. I long ago reached my
level of incompetency and now I just have to sound sagacious and throw out a
few acronyms & buzz words.
Post by henri
think about when you load the front page of ebay
And think about when you try to load the front page of eBay into two
different browser windows simultaneously.
Jim D..
Post by henri
Post by Jim D.
Not necessarily true. The trick is to have one window monitoring the
bidding
Post by henri
Post by Jim D.
and another with a bid ready to confirm. You can do this easily in the
last
Post by henri
Post by Jim D.
6 seconds IF network response time & eBay response time is good.
Don't
Post by henri
Post by Jim D.
try
Post by henri
Post by Jim D.
it at 9PM EST on a Sunday but then automated sniping tools may fail
also,
Post by henri
Post by Jim D.
Some good ones have adaptive bid times. They moitor bid response times
frequently and adapt the bid lead times accordingly.
I haven't found any automated snipe service or software to be totally
dependable. What happens if esnipe needs to place 1000 bids all at 3
seconds to some specific time. Unless it has 1000 different connections
to
Post by henri
Post by Jim D.
the Intenet, they can't be placed simultaneously.
while no software will be totally dependable (i've never used esnipe or
others), i'm not sure you get how internet "connections" work....
there is no limit to how many concurrent requests your computer can make
well, there is, and it is set by the operating system and how much
memory/cpu/resources you have available at that moment in time - and it's
more than 1000, closer to 32,000 on a standard unix machine)
think about when you load the front page of ebay: you are in fact making a
request for each image on the page and you are making all those requests
at the same time, yet you only have "one internet connection".
henri
Kenbo
2005-05-15 22:39:29 UTC
Permalink
On Sun, 15 May 2005 17:55:08 -0400, "Jim D."
<***@removeYahoo.com> wrote:

[...]
Post by Jim D.
Where are the communications engineers when you need one? I'm no computer
scientist, but somebody please explain to me what happens when a message is
sent via an application protocol like HTTP over TCP/IP over a T-1 or cable
modem and how fast such messages can be successfully exchanged.
TCP is pretty inefficient. There is a lot of handshaking overhead to
set up and tear down connections. How fast? That depends a lot on cpu
speed and utilization, available bandwidth, other traffic, number of
hops, router efficiency, retries, application balancing of
responsiveness vs. throughput maximization, etc. and an exact answer
in the general case is impossible to give. I work in the realtime
world where TCP is often avoided when determinism is required, and
where TCP must be used access to the network is tightly controlled. In
my experience on the QNX operating system TCP is 2-3 times slower than
native network protocols even when two nodes are wired back-to-back
with no intermediate hops.
henri
2005-05-16 02:26:07 UTC
Permalink
I'm one of the system architects for cisco's eLearning web-portal if
that's worth anything.

i'm not sure what you mean by "cpu requests".
Post by Jim D.
Post by henri
Post by Jim D.
Post by henri
Post by Jim D.
I haven't found any automated snipe service or software to be
dependable. What happens if esnipe needs to place 1000 bids all at 3
seconds to some specific time. Unless it has 1000 different
connections to the Intenet, they can't be placed simultaneously.
i'm saying that a single computer can make more than 1000 simultaneous**
http (ie web) requests to ebay's servers given one internet connection

** where simultaneous means within milliseconds of each
other. the requests themselves are sent one after the other unless the
machine has more than one cpu and/or network card.

again, from the point of view of esnipe the placing of the request is much
more important than when the response from ebay comes back.

lets break it down:

step 1: esnipe sends out request
step 2: ebay receives request
step 3: ebay processes request
step 4: ebay responds to request
step 5: esnipe receives response


so, assuming #1 can happen simultaneously (for all intents and purposes),

step #2 depends on network traffic and the servers accepting the requests,
assuming no Denial of Service attack is going on both should be fine

step #3 by process i mean: lets assume that ebay is smart (a stretch i
know, but let me not confuse the software guys with the business guys)
they accept the connection and then process it. if the processing is
backed up or slow due to load they still have the time stamp of when they
accepted the request and will use that time stamp instead of when they get
around to actually processing the request

step #4: this is where we see a slow down on sunday nights, just because
the rendering of the page takes some time (get the auction text, get the
current high bid, get the number of bids, update the time left, put it
all together, etc) does not impact when the bid was placed. This could
take 30 seconds from esnipes point of view and they wouldn't care, all
they care about is that the bid got posted when they sent it

step 5 again depends on network traffic between ebay and esnipe


i'm sticking to: esnipe can handle placing thousands of bids on the exact
same auction at exactly the same time and ebay will handle it as
long as there are not network and/or server glitches. (well, also as long
as both sides don't have total idiots writing the code)

henri
Post by Jim D.
I get the feeling you're talking about CPU requests and I'm talking about
application requests. Different animals. No question a CPU can process
millions of instructions per second. Even billions nowadays. And, high
speed Intenet connections pass The bottleneck isn't processor speed. It's
the size of the pipe, the efficiency of the communications protocol, and the
ability of the receiving party to process the request once it receives it. I
guarantee you that come Sunday evening eBay's ability to process is
diminished by the sheer volume of messages. Not as bad as it used to be as
when they were growing faster than they could install hardware but
noticeable nonetheless.
Where are the communications engineers when you need one? I'm no computer
scientist, but somebody please explain to me what happens when a message is
sent via an application protocol like HTTP over TCP/IP over a T-1 or cable
modem and how fast such messages can be successfully exchanged.
Jim D.
Post by henri
i'm sorry, but all the REQUESTS _do_ occur simultaneously (for all
intents and purpose, i'm sure they don't happen within the same cpu
instruction, but at XXXmhz it happens so quickly that it basically is
simultaneous).
your example shows that with a slow connection the RESPONSES do not
complete simultaneously. not the same thing.
esnipe doesn't really care about the response (well, they do, but it is
not time critical)
so from the point of view of esnipe and ebay there is no real limit to
how many people they can have bid on the same auction with only 3 seconds
to go (like i said earlier, the limit _might_ be around 32K per computer
esnipe is using to send bids to ebay)
henri
Post by Jim D.
Although I have been working with computers for 40 years, there's
definitely
Post by henri
Post by Jim D.
a lot I don't know. When people start talking about pipelining,
persistent
Post by henri
Post by Jim D.
connections and transport compression, my eyes glaze over. However, one
thing has not changed in 40 years. You can't put 10 lbs of manure in a
5
Post by henri
Post by Jim D.
pound bag. Yes, you can initiate a single request that causes many
links to
Post by henri
Post by Jim D.
be loaded but the subsequent events do not occur simultaneously. Events
can
Post by henri
Post by Jim D.
occur in very quick succession, of course. When you load a page, the
viewer
Post by henri
Post by Jim D.
is making a single request but a series of requests usually go off after
the
Post by henri
Post by Jim D.
initial request to gather, execute, and/or display all the components.
You
Post by henri
Post by Jim D.
can see this when you load a page with a lot of images on a slow
connection.
Post by henri
Post by Jim D.
Neither the links nor the displays are executed simultaneously but
sequentially as the process is ultimately limited by the communications
protocol.
Unfortunately, if you want to get into a discussion of the relationship
of
Post by henri
Post by Jim D.
HTTP and PPP & HDLC over TCP/IP, I'm not your man. I long ago reached
my
Post by henri
Post by Jim D.
level of incompetency and now I just have to sound sagacious and throw
out a
Post by henri
Post by Jim D.
few acronyms & buzz words.
Post by henri
think about when you load the front page of ebay
And think about when you try to load the front page of eBay into two
different browser windows simultaneously.
Jim D..
Post by henri
Post by Jim D.
Not necessarily true. The trick is to have one window monitoring the
bidding
Post by henri
Post by Jim D.
and another with a bid ready to confirm. You can do this easily in
the
Post by henri
Post by Jim D.
last
Post by henri
Post by Jim D.
6 seconds IF network response time & eBay response time is good.
Don't
Post by henri
Post by Jim D.
try
Post by henri
Post by Jim D.
it at 9PM EST on a Sunday but then automated sniping tools may fail
also,
Post by henri
Post by Jim D.
Some good ones have adaptive bid times. They moitor bid response
times
Post by henri
Post by Jim D.
Post by henri
Post by Jim D.
frequently and adapt the bid lead times accordingly.
I haven't found any automated snipe service or software to be totally
dependable. What happens if esnipe needs to place 1000 bids all at 3
seconds to some specific time. Unless it has 1000 different
connections
Post by henri
Post by Jim D.
to
Post by henri
Post by Jim D.
the Intenet, they can't be placed simultaneously.
while no software will be totally dependable (i've never used esnipe or
others), i'm not sure you get how internet "connections" work....
there is no limit to how many concurrent requests your computer can
make
Post by henri
Post by Jim D.
Post by henri
well, there is, and it is set by the operating system and how much
memory/cpu/resources you have available at that moment in time - and
it's
Post by henri
Post by Jim D.
Post by henri
more than 1000, closer to 32,000 on a standard unix machine)
think about when you load the front page of ebay: you are in fact
making a
Post by henri
Post by Jim D.
Post by henri
request for each image on the page and you are making all those
requests
Post by henri
Post by Jim D.
Post by henri
at the same time, yet you only have "one internet connection".
henri
PDX_Pinball
2005-05-17 14:34:36 UTC
Permalink
Thanks for all the help. I ended up taking that average TCP/IP request
time, multiplied by the coefficient of the esnipe CPU megahertz speed,
divided by Pi and plugged that into Abel's thereom which gave me the
answer of 4 seconds. I used that as my buffer time and was the high
bidder. It also helped that I was the only person to place a bid in
the last two minutes of the auction.

Bob

Matt Hoffman
2005-05-14 19:23:33 UTC
Permalink
I always set it for 3 seconds, and have never had a problem. Well,
except when my bid is too low. :)
Post by PDX_Pinball
I'm using esnipe for the first time and want to see what kind of buffer
time everyone uses. The default is 6 seconds, but not sure how close I
can cut it. Suggestions?
Karl
2005-05-15 00:27:15 UTC
Permalink
Buffer time greatly depends on what size motor you are using for what
size cloth wheel. For pinball use I would recommend at least one hp
(horse power) grinding motor or more better yet. The bigger the motor
however, the bigger the wheels you can spin and the faster you can
buff. It all depends on your buget.

Happy buffing, Karl.
Ben
2005-05-15 02:28:35 UTC
Permalink
Post by Karl
It all depends on your buget.
Is that anything like a bugel? ;-)
Loading...