AppBeat Website Speed Test (Beta)
We have published first beta version of our Website Speed Test. This tool allows you to open any website on remote web browser where it is analysed for performance. At the end you get summary report for selected geographic location.
Currently we support three remote locations:
New York (US East) South Korea (Asia Pacific) Slovenia (Central Europe) This tool can give you insight how your page behaves for visitors from different regions.
Coming very soon: Website Speed Test
We are currently doing final internal review of our API for synthetic website speed testing!
var harResponse = AppBeat.PageSpeed.API.RunTest(test.PublicId, test.Url, test.Location);
We have build entire infrastructure for this from grounds up in record time. We will provide multiple test locations and simple page for everyone to use.
Later we will provide special REST API for website speed testing and we will also integrate this functionality into AppBeat monitoring as free bonus.
Tips & Tricks: bulk importing your website monitors
Few customers who previously used competitive solution asked us if we can help them migrate their web site monitors to AppBeat. We helped them of course and in this process we also created internal tool which speeds up this migration.
If you have too many websites to import them manually, please just contact us and we will gladly assist you. Why bother with manual work if we can do it automatically!
Free 1 minute website monitoring
For those users who are using our free service, we are giving you additional choice. If you want to have one minute website monitoring instead of five minute interval, we can offer you this for free, if you are good with just one web monitor.
To summarize: you can have 5 x five minute website monitors or we can offer you 1 x one minute web site monitor - for free of course.
C# - how to lock without deadlocks
In C# there is built-in keyword lock which enables you to create thread-safe methods. However, you must be aware that if you are not careful, you can create deadlock conditions where your method waits for lock indefinitely.
How lock keyword works? As described in “Locks and exceptions do not mix” blog article, in C# 4 compiler translates lock statement into this:
bool lockWasTaken = false; var temp = obj; try { Monitor.