 43 | , however there are quite a few "spikes" in the performance where we are getting a lot of very slow ... with uniform set of queries and the performance is OK in some cases and is slow in others. Also, the slow ... . Each time at the same time we see these slow response incidents. The system seems to destabilize |
42 | ), but it seems to be very slow. The database is quite empty now, just between 5-20 records / entity, but it's still very very slow. That's the only thing that is slow on my server... How can I speed it up? It's sooooo slow. It takes ages to open an entity or to refresh data. It shouldn't be so slow. Try with firewall |
40 | to get candidates for querying the primary key. This is the slow part. I'm looking for a way to optimise ... milliseconds. If ORDER BY is removed, the queries run very fast The second query is slow |
40 | it up? Your test becomes slow as the database is filled. Every task run includes: Execution |
40 | Hi, I have found a strange behavior when merging entities with "mapped by" set on @OneToMany relation. Even if object is fetched with find on the same transaction, merge is very slow. It's because on merge every single relation marked as LAZY is fetch from database. Attached two examples |
40 | - This code is tested on Windows and Mac. Windows is working great, Mac is very slow (read is 11 seconds on Mac, and 100 milliseconds on Windows). - Application is using Spring Boot console application (for JPA implementation) - MacOS Sierra 10.12.3, Core i7 CPU, 16GB RAM, SSD drive java version "1 |
38 | Mapped By Fetch is very Slow |
38 | Out of Memory - Slow leak? |
38 | Queries are slow on a large database |
38 | slow performance for a complex query |