Poor model save performance due to cascade change in 1.5.0 (probably)?

Is anyone else experiencing poor model save() performance? It seems to start happening when you get past a certain number of objects (hundreds) reachable by OneToMany or other relationships. In v1.4.4 and previous I do not think this was an issue, but we're seeing some requests time out because of this now (i.e. save() calls taking upwards of 30 seconds to complete).

I suspect it may have something to do with part of the change in #1113 but I'm not familiar enough with the saveAndCascade() code to be sure.

Right now our somewhat sad workaround is to add this method to most model objects and call it instead:

    public void fastSave() {
        String dbName = JPA.getDBName(this.getClass());
        if (!em(dbName).contains(this)) {
            em(dbName).persist(this);
            PlayPlugin.postEvent("JPASupport.objectPersisted", this);
        }
        willBeSaved = true;
    }

P.s. So glad to see people still working on Play 1! It's still my favorite web framework by far. Thank you!

Start by reading the saveAndCascade() code and the changes discussed in #1113, then compare its behavior with the reported fastSave() workaround. Reproduce save() with hundreds of objects reachable through OneToMany or other relationships and measure whether the operation still takes over 30 seconds or times out.