May 2, 2008 -- (WEB HOST INDUSTRY REVIEW) -- Canadian web hosting provider Cirrus Tech (cirrushosting.com) has recently installed new Dell PowerEdge Blade Servers in its Toronto, Caanda data center.
Level 1 PCI DSS Certified Service Provider! DataPipe delivers the best network & support; top tier data centers; New York metro, Silicon Valley, London, Hong Kong, Shanghai. DataPipe - Personal Touch, Global Reach.
Dell says its PowerEdge Servers are "The World's First Fully Modular, Most Power Efficient Blade Solution." Cirrus says it will take full advantage of these technologies.
Blade servers are much sleeker than rack-mounted servers and are designed for high density. But unlike a rack-mounted server that can essentially stand on its own, a blade server needs an enclosure that houses other blade servers.
And while the standard non-blade servers duplicate components among each server, blade servers share the non-core computing services between them, saving the data center a significant amount of energy.
"Our decision to purchase the PowerEdge Servers made sense from both a business standpoint and an environmentally conscious perspective," says Ali Mirdamadi, product director at Cirrus Tech. "The Dell PowerEdge Servers consume 19 percent less power and perform 25 percent better per watt than competing products. Cirrus hopes to pass on these energy savings to its clients."
In addition to energy efficiency, the PowerEdge Servers allows data centers a greater level of scalability, load balancing and redundancy. Cirrus Tech says it will introduce new services that will fully benefit from this technology.
Currently, the PowerEdge Servers are being tested at Cirrus Tech's Toronto data center.
Search the Knowledge Base to find a solution to your problem.
Browser
CCBot/1.0 (+http://www.commoncrawl.org/bot.html)
Remote Address
38.103.63.17
Referrer
Date/Time
12-May-08 03:50 AM
Stack Trace
at cfart_whnews_Close2ecfm1364004782.runPage(D:\home\thewhir\html01\templates\art_whnews_Close.cfm:72) at cf050208_Cirrus_Tech_Installs_Blade_Servers2ecfm113192346.runPage(D:\home\thewhir\html01\marketwatch\050208_Cirrus_Tech_Installs_Blade_Servers.cfm:1)
coldfusion.xml.XmlProcessException: An error occured while Parsing an XML document.
at coldfusion.xml.XmlProcessor.parse(XmlProcessor.java:154)
at coldfusion.runtime.CFPage.XmlParse(CFPage.java:182)
at cfart_whnews_Close2ecfm1364004782.runPage(D:\home\thewhir\html01\templates\art_whnews_Close.cfm:72)
at coldfusion.runtime.CfJspPage.invoke(CfJspPage.java:152)
at coldfusion.tagext.lang.IncludeTag.doStartTag(IncludeTag.java:343)
at coldfusion.runtime.CfJspPage._emptyTag(CfJspPage.java:1908)
at cf050208_Cirrus_Tech_Installs_Blade_Servers2ecfm113192346.runPage(D:\home\thewhir\html01\marketwatch\050208_Cirrus_Tech_Installs_Blade_Servers.cfm:1)
at coldfusion.runtime.CfJspPage.invoke(CfJspPage.java:152)
at coldfusion.tagext.lang.IncludeTag.doStartTag(IncludeTag.java:343)
at coldfusion.filter.CfincludeFilter.invoke(CfincludeFilter.java:65)
at coldfusion.filter.ApplicationFilter.invoke(ApplicationFilter.java:210)
at coldfusion.filter.RequestMonitorFilter.invoke(RequestMonitorFilter.java:51)
at coldfusion.filter.PathFilter.invoke(PathFilter.java:86)
at coldfusion.filter.ExceptionFilter.invoke(ExceptionFilter.java:50)
at coldfusion.filter.ClientScopePersistenceFilter.invoke(ClientScopePersistenceFilter.java:28)
at coldfusion.filter.BrowserFilter.invoke(BrowserFilter.java:38)
at coldfusion.filter.GlobalsFilter.invoke(GlobalsFilter.java:38)
at coldfusion.filter.DatasourceFilter.invoke(DatasourceFilter.java:22)
at coldfusion.CfmServlet.service(CfmServlet.java:105)
at coldfusion.bootstrap.BootstrapServlet.service(BootstrapServlet.java:78)
at jrun.servlet.ServletInvoker.invoke(ServletInvoker.java:91)
at jrun.servlet.JRunInvokerChain.invokeNext(JRunInvokerChain.java:42)
at jrun.servlet.JRunRequestDispatcher.invoke(JRunRequestDispatcher.java:257)
at jrun.servlet.ServletEngineService.dispatch(ServletEngineService.java:527)
at jrun.servlet.jrpp.JRunProxyService.invokeRunnable(JRunProxyService.java:204)
at jrunx.scheduler.ThreadPool$DownstreamMetrics.invokeRunnable(ThreadPool.java:349)
at jrunx.scheduler.ThreadPool$ThreadThrottle.invokeRunnable(ThreadPool.java:457)
at jrunx.scheduler.ThreadPool$UpstreamMetrics.invokeRunnable(ThreadPool.java:295)
at jrunx.scheduler.WorkerThread.run(WorkerThread.java:66)
