Please recommend a desktop system for me, a programmer, for < $1k

[Loren Pechtel]

That's interesting and probably true.

Do you or anybody have a tool to measure when ISP throttling is
occuring? The links Paul provided were not clear about any tool you
can download. The only tool I have is a freeware utility called
BitMeter that simply tracks, in a rough average every hour, your bit
rates d/l and upload in MB/s every hour. I want more tools with
instant real time abilities. I also, for programming purposes, have a
packet sniffer called Fiddler, but it's a bit too granular (it gives
you for example the bit stream packets in Hex coming in or going out).

I wrote a little program to try to trace where the bottlenecks were
occuring and found that when it was acting up the failures were right
at the start but random. I would get a nice bunch of green (typical
ping times) and then it would go mostly black (response lost) for a
while then back to green. Red (delayed response) basically never
occurred once it stabilized.

It doesn't attempt to maintain an open connection with anyone,
though--it's strictly a matter of graphing the results of multiple
tracerts.

 

[RayLopez99]

I wrote a little program to try to trace where the bottlenecks were
occuring and found that when it was acting up the failures were right
at the start but random.  I would get a nice bunch of green (typical
ping times) and then it would go mostly black (response lost) for a
while then back to green.  Red (delayed response) basically never
occurred once it stabilized.

It doesn't attempt to maintain an open connection with anyone,
though--it's strictly a matter of graphing the results of multiple
tracerts.

That's interesting. Are you familiar with Fiddler? It's a freeware
program used to trace packets--maybe you can play around and figure
out how to do the same thing with Fidder, which also has a plug in for
a browser.

But if failures are indeed either green or black, with no red, then
Fiddler won't tell you much more than what you found out with your
homegrown program.

RL

 

[Loren Pechtel]

That's interesting. Are you familiar with Fiddler? It's a freeware
program used to trace packets--maybe you can play around and figure
out how to do the same thing with Fidder, which also has a plug in for
a browser.

But if failures are indeed either green or black, with no red, then
Fiddler won't tell you much more than what you found out with your
homegrown program.

I've never heard of it. I simply whipped up a little program to do a
tracert to a supplied target and then at IIRC 15 seconds ping each
station on the path and record what happens. The objective was a
graph over time to make it clear what was going on. Packets were
either getting through or getting lost, no delays. Ping doesn't retry
packets, though, so the main cause of delays is eliminated.