Yuval Ararat

Continues lerner eager to explore

Stress Testing customisations on AEM Author with Siege

Turns out most of you want to make sure your server will deal with your complex authoring requirements and data structures. In a general sense if you wish to test the capability of your server in reference to the infrastructure and baseline it you should go and run ToughDay and feel all warm and fuzzy. This is a great practice and has been tried and tested many times in many clients proving to have successfully indicated the performance of the system.

But if you are here, you are not looking for the default best practice but a solution to your need, stress testing on small-scale of your code to make sure you wrote something that does not kill the server. It might be a servlet, or a renderer or anything you wish to run on any of your environment. well let me

Siege is a stress testing tool for single URL through bash. if you have not used it in the past read about it here. it is old, but it is also simple and that is its value in the KISS development process.

I truly enjoy it as it allows me to have some insight into a few areas while i develop, simple way of stressing a servlet i just wrote to see if i have memory leaks or ill affects on Tar growth or just watching my server response time as i run maintanance. During the years i found many benefits to it in a small-scale developer scenario.

In edge cases where i know that there is a page that is giving grief on a production environment using Siege has been quite useful, you easily simulate a load in a different AEM instance with the production code and content.

Made some tough to negotiate situations much easier with a quick insight into the problem in an instance you can monitor closely through JMX etc.
All from a command in Terminal whilst you watch the calls go by

When encountering AEM Author performance degradation i have encountered a few hiccups on how i can pass the credentials to siege to make this work.

The most reliable way i found to get the login going was through the config file, depending on the version you installed it will be in different locations. my local make got a /usr/local/bin/siege.config file whilst the ones from brew will get a Cellar location with a siegerc file.

Either way the file format is consistent on all if you are in the latest version (2012 vintage..)

Sample is here https://github.com/JoeDog/siege/blob/master/doc/siegerc.in

I add both the following changes to make sure the login works, you could also use the last login to work as part of the URL list you want the Siege client to run against.

  • login = admin:admin
  • login-url = http://localhost:4502/libs/granite/core/content/login.html/j_security_check POST _charset_=utf-8&j_username=admin&j_password=admin&j_=true

In the configuration you could also add SSL and Proxy when needed.

Hope this is helpful.

Netgear Nighthawk R7000 Review

I was investigating lately my slow Time Machine backups which were having an ill effect on my life. this drove me to look at NAS solutions as a replacement to old faithful 2008 Macbook. But i was a bit more through to verify my real pain point as the specs on most NAS are around the same if not lower than the Macbook dual core 4GB.

Even with its USB 2 drives it was still relatively speedy compared to the network throughput. when working with internal drive speed test.

So what was the real issue? i was wondering long and deep whilst trying many options in the configuration of the Billion BiPac 7404VNOX.

First i was looking at my current wired speed vs the wireless, it gave me the most grim reality, my router was slow! so slow that i was at best writing to the shared drive at 6MB/s and reading at 7MB/s. I was not sure what drove this slowness and in what areas the real culprit lied. I tried to get it to a proper 802.11n speeds to no avail. Wireless 2.4 Ghz channel was clear from competition, signal was strong, SNR was great. what was it?

Long nights and changes in the properties or the reading of many painful other experiences i came to the conclusion that it must be the router itself and that it probably has reached the end of the road for wireless speeds.

I was looking at the top of the market AC5300 and AC3200 dual bands and decided that i agree, there is no real need for more than AC1750 at this point and the AC1900 is quite good for my needs. this is quite counter intuitive to my nature to not buy the latest and greatest and didnt feel initially right. but once i figured out that all my devices just don’t have the latest and greatest network chips in them i was convinced this would be a good choice.

I have had 2 options to choose from in reality.

Asus RT-AC68U and the NETGEAR R7000 Nighthawk AC1900 and even went through a review comparing both, well many reviews comparing them and got to the point that i believe the Netgear was about to supply me better usability due to its features. This review which was giving the indication the Asus is better i was convinced the Netgear was my best option.

Thus i went out to purchase the Netgear Nighthawk R7000 from the local shop.

Once i got it home and dedicated my time to adapt it to my network i figured out how good the system was.

The first steps in the setup including starting the router up and logging in were quite simple and straight from the initial guide supplied. Type the domain name in and you get into the router setup wizard, but it is not that easy as it might be if you don’t use the internal DHCP and have another DHCP at home. What i had to go through is to neutralise my DHCP and finish the setup wizard as there is no way to go into the admin any other way. so 20 minutes after and i got my Router finished and all the nodes connected.

This was a bit of a surprise that the system was stuck in trying to get me to the URL when using the IP and that the setup locked the admin interface until i got through the last submit of the setup wizard.

Most of the things are quite easy and the UI, though not pretty is straightforward, is quite self-explanatory. only thing i had to dig around the web for was how to set the timezone. The trick was to navigate to the advanced tab -> security accordion -> schedule -> time zone and set your timezone and automatically set the daylight savings. job done.

At the end it was not that painful and i got everything, including the power down on timer of the wireless quite quickly setup. This allowed me to resume with my tests to see how did this affect the internet and wireless connection in the house

The biggest surprise was the speed. it was impressive! my internet speed, wired or wireless is amazingly fast, i use to get 40MB/s and i always wondered how is the 100MB/s cable network i pay for can degrade so dramatically to this. But in this test i was at 103MB/s mark which is way nicer and really is the full strength of the cable modem. This was a very nice warm fuzzy feeling.

The file transfer rate which was already maxed out when wired down showed similar write speed of 43 MB/s but the read speed is a bit better at ~80MB/s which is nice but not overly impressive compared with the 73MB/s prior router delivered. The interesting tidbit came to light whilst i was testing the wireless 5Ghz, Now I get 20+ MB/s write and 40MB/s read which is about 3.5 times better than the Billion 7404VNOX router i had before. and even the 2.4Ghz is almost double the speed of the Billion. this was nice.

I have yet to connect a USB 3.0 drive to the router to use as Time Machine backup yet and have not tested other edge features in the space of time that the router is in my possession and i most likely add to this review more information in later stages.

To conclude my thoughts i have to say i feel i have done the right choice, though the interface is not as slick and nicely looking it is very very intuitive and is very robust. some simple things need getting used to such as the DHCP DNS entries that are actually in the WAN settings, or the location of the time settings under security. but once this is done the VPN, File Sharing including time machine and the application for the mobile phone is quite nice. and with the great performance in both wireless and internet gave me the feeling that i made the right purchase decision.