Lumada's stability and performance are pretty good. The limitations I run into are usually with the database that I'm trying to write to rather than read from. The only time I have a real issue is when an incredibly complex query takes 20 minutes to start returning data. It's sitting there going, "All right. Give me something to do." But then again, I've got it running on a machine that's got 64 gigs of memory.

Pentaho is relatively stable, but I average about one failed job every month. 

In terms of the stability of the solution, as I noted, I wouldn't use it for large data sets. But for small to midsize companies that are looking for a low-code solution that isn't going to break the budget, it's a great tool for them to use.

It worked and it was stable enough, once we figured out the little quirks and how to get around them. It mostly handled our production workflows without issue.

We haven't had any problems in particular that I can think of. It is quite a workhorse. It just sits there running reliably. It has got a lot to do every day. We have occasional issues of memory if some transformations haven't been written in the best way possible, and we obviously get our own bugs that we introduce into transformations, but generally, we don't have any problems with the product.

I haven't had any problems with stability. Right now, for the implementation of the Enterprise edition, we're trying to make sure that it's highly available in case anything goes down, and we have proper safety nets in place, but personally, I haven't found any issues.

They are making it a lot more stable. Earlier, stability used to be an issue when it was not with Hitachi. Now, we don't see those kinds of issues or bugs within the platform because it has become far more stable. Also, we see a lot of new big data features, such as connecting to the cloud.

Its stability is very good.

I would rate it an eight out of ten in terms of stability.

The stability depends on the version. At the beginning, it was more focused on stability. As of now, some things have been deprecated. I really don't know why. However, I have been pretty happy with the tool. It is a very good tool. Obviously, there are better tools, but Pentaho is fast and pretty easy to use. 

For all of the features that we have been using, it is a stable product.

The performance is good. I have not done a test on the bleeding edge of the product. We only do simple jobs. In terms of data, we extract it and then exported it from MySQL to the CSV. There were only millions of data points, not billions of data points. So far, it has met our expectations. It's quite good for a smaller number of data points. 

The stability is good. 

There is definitely some lag but with a little improvement, it will be a good fit.

The stability was perfect.

It's been stable.

The stability has been great. Other than for upgrades, it has been pretty stable.

There have been some bugs and some weird things every now and then, but it is mostly fairly stable.

The stability is okay. In the transfer from before it was Hitachi to Hitachi, it was two years of hell, but now it's better.

The stability is not great, especially when you start patching it a lot because things get broken. That is not a great look. When you start patching, you are expecting things to get fixed, not new things to get broken.

With modern programming, you build a lot of automated testing around your solution, and it is specifically for that. I changed this piece of code. Well, what else got broken? Obviously they don't have a lot of unit tests built into their code. They need to start doing that because it looks horrible when they change one thing, then two other things get broken. Then, they released that as a commercial product, which is horrible. Last time, somehow they broke the ability to connect with databases. That is something incredibly basic. How could you release this product without even testing for that?

We are on-prem. Once the product was installed and up and running, I haven't had issues with the product going down or not being responsive.

We have one technical lead who is responsible for making sure that we keep upgrading the solution so we are not on a version that is not supported anymore. In general, it is low maintenance.

The stability is good. We haven't had any issues related to Pentaho.

I think that Pentaho Kettle is a stable software, if it wasn't, we wouldn't have used it (because we don’t like angry customers).

There were no issues with the stability.

The performance for Big Data needs to be improved.

There were no issues with its stability.

There were no issues with the stability.

The product is stable. There are no bugs or glitches. It doesn't crash or freeze. It's reliable. 

It could have been the case that I may not have been doing it the right way.

It's not very stable, at least not in the case of the community edition. I'm working with the community edition right now and I think perhaps it is because of that it is not very stable, it causes the system to sometimes hang. I'm not sure if this is the case for pair tiers.

There are some with stability. As I said before there are some small bugs but it’s Pentaho you can always find workaround for it.

There have been no stability issues.

Stability is a bit of an issue. The GUI quite often ‘freezes’ and the is no alternative to killing the session. Very frequent saving is in order

It's a stable product. In fact, contains some mocks, where you can write your own Java software, and do an ETL, specific for your needs.

No issues.

There were issues, but they were solved with help from tech support.

We haven't had any issues with stability except for those described in the Areas for Improvement.

There was no issues with the stability.

We've had no issues with stability.

Until now, the stability of Pentaho is great. I've already tested various scenarios and I didn't feel a loss of performance.

There have been no issues with the stability.