fey42

My 2 cents.
 
Mostly everybody treats their computers the same, regardless of whether they are at home or at work.
It's working don't touch it.
Instead, let's keep up on the PM, like something as simple as using a vacuum cleaner and just sucking at all the fan and vent locations.
NOT compressed air and blowing it all in.

Like most things obsolete, Global Warming, Tenured Professors, NWS, etc., it is called publish or perish.
 
Adobe, a long time ago, served the greater common good, now they can't program their way out of a wet paper bag.
Witness the constant updates to their software that works most of the time or the switch from selling software to renting software.
The almighty $ rules.

Your problem might not be your local ISP. Since they have to connect across the country you are at the mercy of every connection made and every node you pass through. They have control over everything until they hand it off to the Internet backbone and then all bets are off, It can go anywhere. I live 70 miles south of Portland, but to get to the Portland Netfix server, I go though Seattle and sometimes San Jose.
 
Also you have time of day that affects speed. Imagine as everyone comes home, has supper and kicks back to stream their favorite show. It starts first on the East  Coast and the load picks up as you move West. 7PM is the worst, the whole country is streaming and unless the server is in your back yard you are in trouble.
 
Try your test against multiple test sites and time of day. You will see a wide variance the further away you are from "home" and the time of day.

Your problem might not be your local ISP. Since they have to connect across the country you are at the mercy of every connection made and every node you pass through. They have control over everything until they hand it off to the Internet backbone and then all bets are off, It can go anywhere. I live 70 miles south of Portland, but to get to the Portland Netfix server, I go though Seattle and sometimes San Jose.
 
Also you have time of day that affects speed. Imagine as everyone comes home, has supper and kicks back to stream their favorite show. It starts first on the East  Coast and the load picks up as you move West. 7PM is the worst, the whole country is streaming and unless the server is in your back yard you are in trouble.
 
Try your test against multiple test sites and time of day. You will see a wide variance the further away you are from "home" and the time of day.

Your problem might not be your local ISP. Since they have to connect across the country you are at the mercy of every connection made and every node you pass through. They have control over everything until they hand it off to the Internet backbone and then all bets are off, It can go anywhere. I live 70 miles south of Portland, but to get to the Portland Netfix server, I go though Seattle and sometimes San Jose.
 
Also you have time of day that affects speed. Imagine as everyone comes home, has supper and kicks back to stream their favorite show. It starts first on the East  Coast and the load picks up as you move West. 7PM is the worst, the whole country is streaming and unless the server is in your back yard you are in trouble.
 
Try your test against multiple test sites and time of day. You will see a wide variance the further away you are from "home" and the time of day.

Your problem might not be your local ISP. Since they have to connect across the country you are at the mercy of every connection made and every node you pass through. They have control over everything until they hand it off to the Internet backbone and then all bets are off, It can go anywhere. I live 70 miles south of Portland, but to get to the Portland Netfix server, I go though Seattle and sometimes San Jose.
 
Also you have time of day that affects speed. Imagine as everyone comes home, has supper and kicks back to stream their favorite show. It starts first on the East  Coast and the load picks up as you move West. 7PM is the worst, the whole country is streaming and unless the server is in your back yard you are in trouble.
 
Try your test against multiple test sites and time of day. You will see a wide variance the further away you are from "home" and the time of day.

That's not fair, you expect me to read everything golly gee whiz..
Hard to make it stand out more unless it was BOLD and italics also.
 
That would be my problem, not the program.
Having made the mistake once, I kept on repeating it.
 
I was trying to get a good window around prime time, that starts on the East Coast at 7PM and ends at 11PM West Coast.
All cleared up.

I believe the wording [in red] requires a bit of a tweak. As tests can be run 100 cycles (or times) at 15 minutes or more frequency, not less, if less, than 15 then a maximum of 50 tests will run. Either way the meaning is the same, however it can be a bit 'intriguing' at first. 

I understand. 
All I can personally say until @CA3LE chimes in, is that if you choose every five minutes, the limit is 50 tests,anything below 30 minutes will be limited to 50 tests, as it states in red,  if you choose thirty minutes, then the limit is raised to one hundred tests. Throttling, considering the vast amount of users that can be testing at one time. 
 
Go ahead and try the setting I suggest if you would not mind. 

My 2 cents.
 
Mostly everybody treats their computers the same, regardless of whether they are at home or at work.
It's working don't touch it.
Instead, let's keep up on the PM, like something as simple as using a vacuum cleaner and just sucking at all the fan and vent locations.
NOT compressed air and blowing it all in.

First I am being brand spanking new to all of this.
Second I am trying to resolve a Netflix streaming issue for a neighbor who doesn't even know where to begin (I'm just slightly smarter). His dataset is hjb44.
Third I have been using TMN for three days now and love it. It showed the problem the very first run. His download was all over the map from 8Mb to 750Kb.
 
Instead of testing to San Francisco I would like to test to someplace closer, in fact I know the IP address of Netfix in Portland, but tracert quits after the third hop.
I live just 70 miles south, I know that has zero bearing on the issue; I am at the mercy of routing. Did a tracert to oregonlive.com (Portland newspaper) and it went to Seattle, to San Jose, then to Portland.
 
How do I go about using one of the Mercury Test Site? Is that portion of code even working?
Remember I warned you I am brand new at this.
 
Thanks, Fred

I am off to do it and restart the testing. I figured that might have been the problem.
 
Thanks, Fred

It was working fine if you look at my log. I did delete some entries BTW..
 
I was switching between wired and WiFi and forcing some tests, which worked, but when I set it back to automatic, it runs the first test and no more. If you look at my log, you can see a string of 1 hour tests and then some forced tests.
 
Since I was running TMN at a friends house I pulled up your site at my house later to see the results and found the problem. So I tried running it at my house last night and only the first test worked.
 
Is this because I am trying to use TMN from two different IP addresses, with the same login,  and confusing the program?
 
Should I create him an account?   If I do that can I still look at his results and not upset the apple cart?
 
We are trying to resolve why his WiFi is dropping so low during prime time.
 
Thanks, Fred, fey42