| *&"& !! We are thrilled to announce a new era for HP UCMDB and UD customers! Effectual has recently completed an extensive series of tuning and optimizations against the MySQL version of the HP Data Flow Probe with these amazing results: • !+!!• • Since it is important to us that you learn more about Effectual’s services and solutions, and our dedication to the best possible customer outcome with HP Software, we have provided a !! free for your use. !)" The Probe (as it is commonly referred to) is not just a process sitting on a box, but a whole ecosystem. And yet it has been completely . And we ignored it too. Until recently. So we did some testing. Then some tuning. Then a lot more testing. We observed, learned more about MySQL and made a little change, then tested each change. Over 700 times. And we think you’ll find the results surprising. '#$#"!% ##( And since the shortcomings of the Probe are often misinterpreted as shortcomings of HP UCMDB , our findings may just change your understanding of the use cases, and enterprise business value, of the entire application. Over the course of a series of blog posts like this one, we will be sharing our findings and explaining in detail how they affect . There are two important things we want you to take away from these blogs: That !# for your organization and, more importantly, that make these changes to your Probes.
Transcript
|
We are thrilled to announce a new era for HP UCMDB and UD customers! Effectual has recently completed an extensive series of tuning and optimizations against the MySQL version of the HP Data Flow Probe with these amazing results:
•
•
•
Since it is important to us that you learn more about Effectual’s services and solutions, and our dedication to the best possible customer outcome with HP Software, we have provided a
free for your use.
The Probe (as it is commonly referred to) is not just a process sitting on a box, but a whole ecosystem. And yet it has been completely . And we ignored it too. Until recently. So we did some testing. Then some tuning. Then a lot more testing. We observed, learned more about MySQL and made a little change, then tested each change. Over 700 times.
And we think you’ll find the results surprising. And since the shortcomings of the Probe are often
misinterpreted as shortcomings of HP UCMDB , our findings may just change your understanding of the use cases, and enterprise business value, of the entire application. Over the course of a series of blog posts like this one, we will be sharing our findings and explaining in detail how they affect . There are two important things we want you to take away from these blogs: That for your organization and, more importantly, that make these changes to your Probes.
|
In a word, . If you’re an HP UCMDB, BSM/RTSM or UD customer using a MySQL version of the Data Flow Probe, the moment your Probe database passes a certain size these problems start, compound, and get worse over time. The threshold for these Probe performance issues is surprisingly low. This is never a question of , but rather just a question of . For many HP UCMDB customers the issues below aren’t a list of problems that happen, but problems that they have lived with for several years.
Below: The query to determine the database size processes more than three times greater data, more than sixty two times faster after tuning.
|
•
•
•
•
•
•
•
•
•
•
•
, the mechanical logging change, and proper sizing of the memory and available resources. The impact is . While these changes may appear simple – and essentially they are – the benefit and positive impact on your business and HP Software experience is gigantic.
|
Pictured below are the results of two of our production integration jobs. Both sets show that the previous (un-tuned) version of the job is far slower than our current (tuned) job.
These are actually and complex jobs. So why share only these big jobs? Our normal, everyday jobs (such as those moving IT Process Records from Service Manager to the CMS) These regular-sized jobs are now so fast that they don’t even show up in the HP UCMDB data access layer log.
When looking at the results above, keep in mind that were added for the purpose of these outcomes. Only database changes were included. These larger jobs perform
with additional server memory and processing resources.
|
Our completely free includes: A detailed guide to removing the mechanical problem from your Probe, a tuning section, a replacement my.ini configuration file, and SQL queries you can run to maintain the best possible discovery or integration/federation Probe available
Join our new twice-monthly Probe Tuning Demo meeting, scheduled for the second and the fourth Wednesday of every month at 8AM Pacific Time Zone (GMT -8:00).
https://global.gotomeeting.com/join/196657325
Effectual can also repair your entire environment and perform these changes for you remotely at very low cost in a few hours.
Effectual Systems Group is an HP partner that provides automation and solutions for HP UCMDB, ITAM, ITSM, and specializes in creating Configuration Management Systems for some of the world’s largest, savviest, most complex IT enterprises.
Contact Effectual’s Solutions Director, Chris Hanson, at [email protected] or 510-323-2174 to learn more about the Effectual CMS and drop-in adapters for ITAM, ITSM and HP UCMDB. Our CMS solution can instantly save you thousands of hours of development and consulting.
What are the specific reasons why Probe performance was so poor for so long? Why didn’t anybody notice until now? Why Effectual? How can the recommended changes all of the serious problems and pain points you’ve experienced with the Probe?
