Intel Atom D945GCLF - First Results!!

[Hulk]

**********************************
(Untangle request for the gamers) Please add this.
Gaming mode like in Bitdefenter antivirus.
Works like this.
Access Untangle Box via browser, but with extra info:
http:\\192.168.1.1\gamersaccess
Login or just gaming password (setup before hand in untangle)
Leave browser open it's the trigger or controller.
As long as browser has socket connection to untangle box
allow that PC to bypass filtering or do level 2 filtering only.
Just close internet browser session when done playing.
you are back to full filtering.
**********************************

Works great for workgroups or single gamer.

Had issues with ping time when viewing list of games for COD4,TF2,B2142.
This was after setting my IP in attack blocker( Search game issues in forum for info).

All the server would show up, but there ping time was high. After joining the ping was fine.

A core duo processor in the same configuration showed much better ping in server list and about 10ms better in game.

Example:

Base line NetGear FVS338
30ms Heroes server Ping once game starts 30ms
33ms Owened you
61ms Rest in peace
54ms All Dustbowl map
etc....


Atom 1.5 processor Untangle Box
300ms Heroes server Ping once game starts 45ms with spike intermitantly
270ms Owened you
161ms Rest in peace
454ms All Dustbowl map
etc....


Core Duo 2.0 processor Untangle Box
33ms Heroes server Ping once game starts 33ms
39ms Owened you
71ms Rest in peace
67ms All Dustbowl map
etc....

[swmspam]

Here is a MRTG graph of Untangle 6.1 on the Intel Atom D945GCLF with the single-core Atom 230 (note: the 230 has hyperthreading).

The operating environment is 3 computers, generally used during the day, two of them somewhat heavily.

The CPU load average over 1 day is 0.08 (15 minute) and 0.10 (5 minute). The graphs are logarithmic. On the load average, the blue line is 5 minute load and the green shaded area is 15 minute load. On the eth1 graph, the blue line is incoming data and the green shaded area is outbound data.

I haven't exactly determined (without more sophisticated techniques) what causes the CPU utilization spikes. Notice the two large CPU load averages at indexes 6:30. Both of these occurred during night and did not have a workload present. This leads me to assume a ClamAV or FreshClam activity was occurring. Closer examiniation of cron may tell.

I will transfer this system to a dual-core Atom 330 and post similar results.