Here’s the sound of not enough infrastructure:
Photo Credit: Pat Pilon Licensed under CC BY 2.0
“What’s going on? I can’t get to the network!”
“The servers are choking and Sales can’t book end-of-month orders!”
“Twitter’s on fire with complaints about our website!”
“We’re getting slammed down here on the help desk! What’s wrong with the network?”
Then here’s the sound of too much infrastructure:
“We overbought on those new servers for the lab. Let’s move those assets around next chance we get.”
Not enough infrastructure = exclamation marks and hand-waving. Too much infrastructure = oh, well.
But it’s not always easy to measure the amount you’re going to need, as we found out when we migrated from our legacy analytics product to Statistica.
Getting the infrastructure requirements right
“It’s right there on the side of the box,” IT said, “where it reads ‘infrastructure requirements.’”
“We see that,” replied the migration project managers, “but there’s a lot riding on this, and we don’t want to get calls in the middle of the night.”
Nobody wanted to hear the sound of not enough infrastructure during a migration project that affected hundreds of projects and users all over the company, so we overbought. Besides, we were confident that, once people saw how much easier it was to use Statistica than our old product, we would see a big increase in our user population, and we wanted to be prepared for that.
But allocating a 12-core server with 148GB of memory to sharing and collaboration? You could almost model weather on that.
We erred on the side of caution, with similar equipment for Statistica execution and Web servers, and Monitoring and Alerting servers (MAS). It turned out to be more than adequate. Since the end of our successful migration project, we see the wisdom in the basic Statistica infrastructure requirements:
Microsoft Windows Server (64-bit) 2008 R2 or later with 2GB of memory, 5GB of disk space and a dual-core processor
Microsoft Internet Information Services, which comes with Windows Server
A standard database, such as Microsoft SQL Server or Oracle, acting as the repository for Statistica metadata
Users can work satisfactorily on even more modestly equipped Windows desktops.
The Great Analytics Migration – new e-book
If you’re planning a migration of your advanced analytics software, have a look at our latest e-book, “Statistica: The Great Analytics Migration, Part 3: Technology.” It poses the main questions every migration project needs to address, then outlines how we at Dell answered them during our successful transition from our previous product (you can probably guess which one it was) to Statistica.
You never want to fall short on your infrastructure requirements, but you don’t want to overbuy, either. Read our e-book to see how best to measure for your migration project.
About David Sweenor
From requirements to coding, reporting to analytics, I enjoy leading change and challenging the status quo. Over 15 years of experience spanning the analytics spectrum including semiconductor yield characterization, enterprise data warehousing, reporting/analytics, IT program management, as well as product marketing and competitive intelligence. Currently leading Analytics Product Marketing for the Dell Software Group.
View all posts by David Sweenor |