|
ElectricAccelerator vs. distcc: samba reloaded
July 20, 2009 — Eric Melski
ElectricAccelerator vs distcc – samba reloaded
In an earlier post I compared the performance of ElectricAcclerator and distcc by building samba using each tool in turn on the same cluster. In that test I found that Accelerator bested distcc at suitably high levels of parallelism, but that distcc narrowly beat Accelerator at lower levels of parallelism. At the time I chalked the difference up to slightly higher overhead associated with Accelerator. But you must have known I couldn’t just leave it at that. I had to know where the overhead was coming from, and eliminate it, if possible. The exciting conclusion is after the break.
Read the rest of this entry »
Posted in ElectricAccelerator. Tags: distcc, ElectricAccelerator, ElectricAccelerator vs distcc, gmake, parallel builds, performance. Leave a Comment »
Public Clouds
July 14, 2009 — martinvr
Today we announced integrations and compatibility with public cloud computing – specifically Amazon EC2. Cloud computing is a hot topic right now, and rightly so. It provides an easy to deploy, cost-effective, scalable, on-demand computing infrastructure –very timely, given shrinking or frozen IT budgets. I can’t count the number of customers who tell me that compute infrastructure is their #1 bottleneck. At Electric Cloud we have years of experience with internal or “private” clouds (after all, it’s in our name). We help customers set up private clouds, some with hundreds of machines, to accelerate and automate their software build and test tasks. It made sense for us to add public clouds to the mix. You can read the press release here.
Our customers gave us some interesting use cases for using our products in combination with the public cloud. Here are some of their ideas:
Read the rest of this entry »
Posted in Build-Test-Deploy Best Practices, ElectricAccelerator, ElectricCommander, Software Development. Tags: Agile, amazon, amazon aws, amazon ec2, cloud, Cloud Computing, software build, software test, test automation. Leave a Comment »
When is Open Source not Enough?
July 8, 2009 — Anders Wallgren
I recently contributed an article to CM Crossroads on when (or whether) to upgrade from an open source Continuous Integration (CI) system to a fully automated enterprise system. It’s a question we get a lot. To help our customers assess their needs, I always start by asking these seven questions: Read the rest of this entry »
Posted in Build-Test-Deploy Best Practices, ElectricCommander. 2 Comments »
Java One was Cloud Crazy
June 10, 2009 — martinvr
I went to Java One last week and was a bit surprised by the amount of cloud chatter. I expected to hear a lot about Larry Ellison and Scott McNealy on stage together. I expected melancholy predictions that this would be the last Java One. I did not expect to hear everyone talking about cloud computing. Don’t get me wrong, I knew that Sun was going to talk about cloud computing. The Sun booth had several stations dedicated to the subject and the Sun store was selling cloud t-shirts. The thing that got me was how many participants were talking about the cloud. All of the technical sessions that had anything to do with cloud computing were packed. Even more surprising was the fact that the sessions extolled the virtues of Amazon EC2 even though Sun is working on their own Cloud offering. I sat through three sessions where the first half hour was dedicated to “Amazon 101”. It looks like Amazon is where real solutions are being created for now but there is definitely competition on the way.
Posted in Uncategorized. Tags: amazon, cloud, java one. Leave a Comment »
The “last mile” – It often seems like 10
June 2, 2009 — Erin Curtis
[This is a guest post from an Electric Cloud technology partner: Daniel Nelson, VP of Products at Phurnace Software (www.phurnace.com)]
In the software development lifecycle the results need to ultimately get out into production. The application must make it onto the server, the server needs to be configured and all of the properties, paths and settings need to be correct to get the value of the application. Those in the data center often refer this to the last mile. And it is often a real bear. Seems more like 10 miles at times. Sophisticated and robust tools like ElectricCommander have automated almost all of the steps in the process, but rely on home-grown scripts to lay the applications down on app servers. Why? It is actually a logical approach if you have no alternative. Every environment is different. Every app has different settings for WebSphere (or WebLogic or JBoss) and there is no way to anticipate those differences. Therefore – the last mile is unique to each customer and each app –the IT or dev teams write scripts. It takes skilled resources and the scripts are always in need of attention. Not anymore. STOP. That is no longer necessary. What if ElectricCommander could hand off the EAR file to a software tool that has already pre-built a model of the environment and has made all of the JDBC, JMS, and application bindings for you? What if it required NO scripting? What if the “last mile” was now automated and under the control of your build and release system? Ta Da ! It is now. Phurnace Software is an auto deployment and configuration tool that will eliminate custom scripting. And you can drive it all from within ElectricCommander. The last mile is now just a step away.
- Daniel Nelson, VP of Products, Phurnace Software
Posted in Build-Test-Deploy Best Practices, Software Development. Tags: deployment, Java, WebSphere. Leave a Comment »
JavaOne 2009
June 1, 2009 — Erin Curtis
Planning to head to JavaOne this week? Stop by our booth in the Expo Hall and say hello. We’ll have product experts on hand to show you our latest and greatest solutions for Java development. Come see us at booth #304.
http://java.sun.com/javaone/
Posted in Uncategorized. Tags: Java. Leave a Comment »
Annocat: e pluribus unum
May 27, 2009 — Eric Melski
ElectricAccelerator annotation files are a fantastic way to get a grip on your build behavior and performance, but what if your Build (capital B) spans more than one invocation of emake? Annotation gives you a good look inside any single invocation, but there’s no way to get an overview of the entire process. You can’t just catenate the annotation files from subsequent emake runs — the result won’t be well-formed XML, and the timing information for jobs in each subsection of the build will reflect time from the start of that subsection, not from the start of the logical build. Plus, you run the risk of having overlapping job identifiers in different subsections. What you need is a specialized version of cat that is annotation-aware. In this article I’ll introduce annocat, a simple Perl script I wrote for just this purpose, and I’ll explain how it works.
Read the rest of this entry »
|