DIMES v0.3.9.9

[CaptainMooseInc]

A new DIMES agent is out... I have NO CLUE what the update entails but I'm hoping it fixes the graphing problem for AMDs and maybe activates some new features???

http://www.netdimes.org/Updates/DimesInstall-0-3-9-9.exe

Nothing too cool as of yet with my poking around....

I will respond later when I am home stating whether or not this new program fixes the graphing problems I have been having!

-Jeff

[PY 222]

I have noticed that even with more agents, one is not guaranteed of more measurements.

For example, brianhiggins and myself. Both of us have 6 agents. Brian has 7 but one isn't producing anything. So equal number of agents but his daily measurements are in the 30k range where as mine is a lowly 10-15k range. I know I am on a fat enough pipe that bandwidth isn't really an issue.

So what gives? And will this new agent be more efficient?

Anyone care to answer?

[brianhiggins]

PY 222

I'm running v0.3.9.9 (previously v0.3.9.7) on six machines using the default settings (30sec delay / UDP protocol)

I believe the original v0.3 defaulted to 60sec delay so if you're using that version it might explain the difference as my output's more than doubled since upgrading.

Brian H.

[CaptainMooseInc]

PY 222, have you gone into the preferences of all of your clients and changed the time inbetween measurements from 30 seconds to 15 seconds???

That's how I'm getting 17,000 measurements/day with only 4 active clients. I'd also suggest (since you claim to have the spare bandwith) to JUMP the kb/s transfer rate to 51Kbps. On a cable modem or DSL connection this should effect NOTHING. I'd turn DIMES off though if you want to game at all, it seems to effect FPS really bad with the internet connections it tries to make.

Picture has been posted.

-Jeff

[PY 222]

Brian, the difference in version might explain the difference in output. I've upgraded 3 of my Agents to the latest v0.3.9.9 and will do the same for my other 3 at home.

CaptainMooseInc yes I have configured all the v0.3.9.9 clients to what you have shown. Thank you for that information.

With the upgraded agent, decreased time between measurements and increased bandwidth, lets see if my measurement rates climb by the end of today.

Onwards people. :thumbs:

[CaptainMooseInc]

Yeah, 2 more agents should be doing more than 2,600 more measurements than me PCZ. :)

You figure I've got 4 clients running with 9,000 measurements today...that's 2250 so far per machine. You've got 6 running and are only doing 2283. Only 2 of my 4 clients are optimized for the 15seconds/51Kbps though....so I think you'll see around 2500-2700 measurements for the same amount of time.

Using yesterday's numbers I took 17,500 and divided it by 4 (number of machines) and then divided that by 24 (number of hours in a day). I'm doing 182 measurements/hour according to how my clients are setup. You are only doing 208 measurements/hour. Seeing that your machines aren't even optimized I figure your per-machine measurements will jump to around 250 measurements an hour from 208 and once I optimize my other two clients I'll jump to around 215 from 182...

Anyone else follow that math and agree??? I know per-machine measurements won't jump greatly, but hey, 30 more measurements an hour is always good. :)

Also, just because you increase your interval time between measurements doesn't necessarily mean you are going to do more. I have some measurements that take around 25-30 seconds to complete (and a couple that have gone longer). After that you have to wait 15 seconds before another one, then if that takes 15 seconds to complete you have 1 minute passed and only 2 measurements done.

A person w/ 30 second intervals could have one measurement done in 15 seconds, 30 second break, then 15 second measurement again and still have the same number that the "quicker timings" client has done.

The whole goal is to hope and pray that you get quick measurements (not a lot of hops) so you can get 3-4 done/min. Of course DIMES wants hops because they want to map the internet so they wanna see you circle the globe hopping if you could. :)

-Jeff

[CaptainMooseInc]

Well...I'm at home now....

There is a new version of DIMES out but absolutely NO F*@#ING GRAPH for my AMD again.

I am still doing measurements.....but I LOVE that graph and I'm getting extremely TESTY watching my dad's laptop doing it.

-Jeff

P.S. I really wish the project director would update the news section to say what the new release entails and/or come on here and explain why the graph isn't working.

:bonk:

[PY 222]

CaptainMooseInc, I am experiencing the same problem as you.

I've just installed the new client onto 4 agents in the office and everyone was graphing great. Its pretty awesome looking at how the network grows.

But once I got home and installed it on 3 of my agents, nothing was graphing but measurements were being done as from what I can see from the Messages tab.

Now, I don't get it. The version is exactly the same with the same Java version 1.5 with the same OS, XP Pro with SP2. I seriously doubt that its the hardware.

Anybody experiencing this as well?

[Evilmoose]

I have the new agent on all 6 of my home machines and one of them has the same problem. I cant narrow it down either:confused:

I will put it on my work boxes next week and see what happens.

[Evilmoose]

It doesnt seem to graph when useing UDP.
Try ICMP and it should start to graph.

[PCZ]

Evilmoose :cheers:

Swapping from UDP to ICMP has fixed my Agents which didn't draw the graphics.

[CaptainMooseInc]

That is an incorrect statement. The computers at Ivy Tech don't allow for ICMP connections so the program uses UDP and graphs great.

I've tried UDP and ICMP and neither graph.

-Jeff

[PCZ]

No my statement is quite correct.

I have agents which dont graph if UDP is selected.
Changing to ICMP makes the graphs work.

Note I did say "my Agents".

[meep]

erm!... i wondered why output of others had increased so quickly without an obvious increase in agents.... i have done 3 of mine just and ramped up both the bandwidth allowance and frequency of the measurements.

:)

[PCZ]

meep

I am trying to work out why my output is so low.
Some of my agents that appear to be doing work can't be.

[meep]

Yea I have a similar issue - but I think (not including this latest version) I got them all working ok - how i did it i do not know.

I have monitored my home pc's that work 24/7 on dimes with 100% uptime seem to have quite random stats, based on the dimes site stats. I can see the trace routes running on the client, then check them on my firewall (isa), then also see the activity on my router, but the measurements made do not increase. I also see the line stating that the client is uploading/downloading the results and next piece of work with the dimes server. But the points dont seem to appear.

Seems to be a bit buggy to say the least.

I will see how this new version fairs.

[PCZ]

meep

I am in the process of renaming my agents.
Making them unique.

Hopefully that way I can find which agents are not performing.

I have a suspicion that the ones I have running at home are not returning much work at all.

[PY 222]

Originally posted by PCZ
Evilmoose :cheers:

Swapping from UDP to ICMP has fixed my Agents which didn't draw the graphics.

PCZ, I can confirm that by changing from UDP to ICMP has also fixed my Agents. All 3 Agents that wasn't graphing before is now graphing perfectly.

Thanks for the tip. :thumbs:

[CaptainMooseInc]

I'm going to be working with Ohad via PMs to work out my problems.

I think mine might be based on the fact that I'm running ZoneAlarm Pro Firewall. I am still getting measurements but the graph is just not happening. It's either that or my nVidia Graphics Card...

-Jeff

[PCZ]

PY222

It was Evilmoose who came up with the graphics fix.
I was just as foxed as everyone else.

meep

I see my agents working and sending in results to the server but the points don't appear.
Well they do eventually but it is a fraction of what they used to produce.

I am wondering how folks with only half a dozen agents can be scoring so much.

[CaptainMooseInc]

New graphics drivers installed..... NOPE
Uninstalled EVERY bit of JAVA I could from the computer...redownloaded it...installed it...removed previous Java allowances from the ZoneAlarm list and made it approve all the new Java connections....

I'm behind a Linksys firewall too...wonder if that may be it???

-Jeff

Well, between the ZoneAlarm Firewall and the built-in Linksys firewall I think some major UDP and IMCP blocking may be going on that is restricting graphing (why I don't know because I don't think it even has to deal with that). Anywayz, I am waiting to hear back from Ohad about what ports are used for the TMCP and UDP Tracerting so I can allow them on my machine as outgoing only.

-Jeff again

[PY 222]

My bad PCZ, I got the wrong fella. So thanks Evilmoose for the tip.

PCZ, could location be a factor to the reduced measurements with some people and increased measurements from others?

As they map out the Internet further, perhaps there are some places that requires more mapping than others? Its just a guess.

[PCZ]

I'm also wondering if location has got something to do with it.

I've done some work on the agents today upgrading the old v3 clients and changing to ICMP on the clients at home.

Lets see what tommorow brings

[CaptainMooseInc]

Location doesn't mean the client will allocate you less tests. This isn't GomezPEER so....

Maybe you need NICagra??? It's Viagra for your NIC card....

What you could be encountering is a whole bunch of "hops" which make certain clients take a long time to get done with a TRACERT.

Most TRACERTs allow a maximum of 30 hops. If you are located in a great spot there is potential to reach all 30 hops which takes much longer.

Most TRACERTs though will die out around 13-16 hops from my location. Google nailed 17 hops and actually completed. AOL.COM gets up to 11 hops and then it just times out for 4-5 and then it stops because the distance is too far to get a good connection.

You probably are just getting 22-25 hops before it dies out. Find a slow client of yours and then take a few of the IP addresses it lists and jot them down. Open the Windows Command Prompt and type:

tracert 173.213.12.4

where the IP address I listed is whatever you jotted down.

See how many hops you are getting (it'll change every time you do it).

-Jeff

P.S. Don't try that IP address, it's not real. It'll return 3 hops and on the fourth it'll say "destination unreachable".