Saturday, 27 August 2011

Windows 7 with ReadyBoost - Perfect for Virtualization Development.


That is one cool feature in Windows 7 which not many people are aware (actually it existed in Windows Vista), which can improve the performance of VMs and host machine with fraction of cost. Let's me introduce it to you, ReadyBoost. Let me get the quote from Microsoft how they describe this feature.

"Want a simple way to speed up your PC?

Just plug in a USB flash drive or card and let ReadyBoost borrow it. ReadyBoost is designed to help when your PC's memory is running low. Low memory can make your computer sluggish because Windows, which needs a place to stash data, turns to the hard drive. Flash memory offers a speedier alternative.

ReadyBoost works with most flash storage devices. In Windows 7, it can handle more flash memory and even multiple devices—up to eight, for a maximum 256 gigabytes (GB) of additional memory.
"

I am using Windows 7 with ReadyBoost for three Windows Server 2008R2 machines (AD, SQL and SP2010) which configured for SharePoint 2010 and Fast Search. The outcome is very satisfied from results I done in PassMark benchmarking tool.

Here configuration details.
  • 8GB DDR3 Memory
  • i7 processor
  • ReadyBoost (32GB SSD with ESATA)
  • 7200RPM HDD
  • USB 2 for VMs

This is the result of SP2010 running without ReadyBoosts in host machine. The VM and host system response are very sluggish and in not workable condition.




After activated ReadyBoosts in host machine, the result has obvious improved and overall performance (VM and host) is  noticeable.



Of course experience/result may be vary depend on running applications or hardware configuration, but strongly recommended to try it out if you have any spare flash drive or SSD.

Wednesday, 3 August 2011

Ajax Toolkit's TabPanel/UpdatePanel and ReportViewer - panelCreated error

You may receive the error when using the Ajax toolkit and ReportViewer on the page, e.g.


This is because the Ajax control is conflict with the ReportViewer, it will works if you using the .Net ScriptManager. But because you need the ToolkitScriptManager for your Ajax controld, therefore this is not an option.

But that is work around/fix for this error, which is just simply change your ToolkitScriptManager to ScriptMode="Release" and it will work like charm.