Memory test

For one solid week, LV5 was left in a testing state running a Phantom network of 60 devices. Randomisation was set to a low-mid range value which means the network was not overly active. However, there were 343 rebursts over the course of the 7 days and each burst introduced 25 new devices instantly. Bursts are designed to emulate a collection of devices all powering on at the same time, or users logging in and out at the same time. Similar to how schools networks are.

The CPU usage was not measured for this early test, but instead, the memory usage was. At this point of the development of the server engine, it's important to know if there are any potential memory leaks.

The following graph shows the memory usage during this period. (Click for a larger version)

The data shows the servers memory usage is low in comparison to the Agent. Although the Agent itself is not final, it is actually the tool that creates the Phantom network, so I am not concerned by it's high memory usage. My focus is the server which is showing good memory management. It looks after the memory usage well, and over the course of the 7 days, it reduced fractionally. It also highlights that compared with the peaks of the Phantoms as shown by the Agent data, the server handles workloads very well. Given the server will be running 100% of the time, this is reassuring.

The testing done was by no means scientific. Normally a quick snapshot of the memory was done twice a day over the 7 days although occaisionally more was taken each day. The peaks show because at the time of the memory snapshot, a burst may have just happened or the station load was high. The agent will be tested at a later date when running as a service, and without running the Phantom network.

Revisiting the past

For the first time in 4 years or so, tonight I installed LanView 4 on a device and ran it. This may be a surprising fact but it's entirely true. I haven't used LV4 since the last release back in 2008 or 2009. I ran it and I openly admit, I cringed at the interface. It's not exactly slick in the way I'd want it now days. The graphics are tacky and overall it looks pretty bad on Windows 7. I never actually tested it with anything beyond Windows Vista.

Read more: Revisiting the past

Join the team

MST has always been a voluntary organisation who offers free tools for everyone.

As the reboot of MST gets under way, I want to be able to concentrate on the development of LanView and am asking for any volunteers to help me maintain the other aspects of MST.

If you are able to volunteer some time with any of the following areas, please do contact me by clicking on my name above and select the Contact Form.

  • .Net Development
  • MAC OS or Mono Development
  • IOS Development
  • Testing specific areas / modules of LV5.
  • Joomla maintenance
  • Documentation
  • Translation
  • Icon and/or Graphic Design

The Development Continues

Just a quick update. The development continues with the focus being on the LV Engine. It is now ready for the first test and has been packages up as required. The performance of the engine is pleasing especially when compared with LV3 and LV4.

Encryption has been put in place and there are plenty of logging options to help me diagnose the issues that will crop up in the wild.

I am hoping to have the test released to testers this week.

More Articles...

  1. Security
  2. Progress Report