Hello Jakub If that filter doesn't work then you can add another filter, example no older than which can give you more recent tickets or even it can bring you the tickets enough fresh for your requirements just add a time range in the query. This sentence do the trick (tickets not older than 360 days)
created <= -1d AND created >= -360d This is the url generated with that filter and it has very nice results that are common bottlenecks in the current development branch. https://issues.apache.org/jira/browse/FINERACT-2234?jql=project%20%3D%20FINERACT%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened)%20AND%20text%20~%20%22performance%22%20AND%20created%20%3C%3D%20-1d%20AND%20created%20%3E%3D%20-360d%20ORDER%20BY%20created%20DESC Then with the list of tickets and the performance test cases that you can propose and discuss with the community can give more details or even more... you can comment on the tickets promoting the conversation with the reporter, the volunteer that is fixing it and the community, (by the way thank you I have added a note and closed it, because that ticket was stalled since 2016). On the other hand I think that a Java Performance Scalability audit proposal should include the goals and the metrics but expecting from you to do a basic/minimal research and proposal. Something like.. hey we are going to do a performance testing using this Apache Fineract version, with this Database and this is the database version, this OS version, deployed on this cloud with this computing resources (RAM, Storace, vCPUs) and this OS settings, Java settings. Or you can ask the community which is the most common deployment of infra settings (hardware and software) and data volume processed at peak days, so then it can benefit more users with your proposal. Because if you are targeting the percentile that is using Apache Fineract for the 10 millions of users, 100 millions of loan transactions I am sure that this kind of users have their own performance team using APMs like AppsDynamics, New Relic, Dynatrace and using complex infrastructure and settings backed by their own specialized engineers and that information will be jealousy keep in secret, which is something that we don't promote but sometimes the signed NDAs are a lock to retrieve useful information. I hope you can progress on your proposal. Best regards Victor Romero El jue, 3 abr 2025 a las 13:03, Jakub Sławiński (<jslawin...@soldevelo.com.invalid>) escribió: > > Hi, > > Unfortunately, it is not what I am looking for. > The set of old issues from the backlog, general areas for improvement or > challenges older than a decade - these do not sound like something > important or valuable to anyone. > > I think I haven't shared the bigger context with the community. > > What we are looking for is to get one more success case for the service we > are currently tuning up: Java Performance Scalability Audit > > What business problems are we targeting? For example: > 🚀 *Performance-Related Issues* > > 1. > > *Slow Application Response Times* – Users experience delays, leading > to frustration and lost engagement. > 2. > > *High Server Costs Due to Inefficiencies* – Unoptimized code leads to > excessive resource consumption, increasing infrastructure expenses. > 3. > > *Frequent System Crashes or Downtime* – Poor memory management, > threading issues, or resource leaks causing instability. > 4. > > *Unoptimized Database Queries* – Slow or inefficient database > operations causing bottlenecks. > 5. > > *Poor User Experience (UX) Due to Lag* – Slow interactions drive users > away and harm customer retention. > > 📈 *Scalability Challenges* > > 6. > > *Inability to Handle Increasing User Load* – System struggles with > growth, leading to degraded performance. > 7. > > *Lack of Proper Load Balancing and Caching* – Inefficient resource > distribution leading to slow responses under load. > 8. > > *Unscalable Architecture* – Design flaws preventing efficient > horizontal or vertical scaling. > 9. > > *Microservices Bottlenecks* – Inter-service communication issues > causing slowdowns or failures. > 10. > > *High Latency in Distributed Systems* – Delays in API responses, > messaging queues, or inter-service communication. > > 🔍 *Technical Debt & Code Maintainability* > > 11. > > *Legacy Code with Performance Bottlenecks* – Old, unoptimized code > making enhancements difficult. > 12. > > *Lack of Monitoring and Profiling* – No visibility into performance > issues until they cause failures. > 13. > > *Memory Leaks and Inefficient Garbage Collection* – Leading to crashes > and sluggish performance over time. > 14. > > *Threading and Concurrency Issues* – Poor multi-threading > implementations causing deadlocks or slow execution. > 15. > > *Security Risks Due to Inefficient Code* – Performance weaknesses that > also expose vulnerabilities. > > 💰 *Business Impact & Cost Reduction* > > 16. > > *Lost Revenue Due to Performance Issues* – Sluggish applications > reduce conversion rates and customer trust. > 17. > > *Missed SLAs (Service Level Agreements)* – Performance problems > leading to contractual penalties or lost clients. > 18. > > *Unnecessary Infrastructure Scaling* – Overprovisioning cloud > resources instead of optimizing code. > 19. > > *Poor DevOps Efficiency* – Developers wasting time troubleshooting > performance instead of building new features. > 20. > > *Long Release Cycles Due to Performance Issues* – Slow debugging and > testing caused by unoptimized code. > > > > What would I like to see as the results of this particular success story? > For example: > > 1. Cut infrastructure costs by 50%. > 2. Increase the number of clients/transactions handled in a stable manner > without changing infrastructure by 100%. > 3. Decrease the time needed by critical operations by 70%. > > What do you think? Are there any business problems we could help you with? > > Please contact me directly if you are ready to check our services. > > > Regards, > Jakub. > > > -- > > *Jakub Sławiński* > Chief Technical Officer > jslawin...@soldevelo.com / +48 514 780 384 > > > *SolDevelo* Sp. z o.o. [LLC] / www.soldevelo.com > Al. Zwycięstwa 96/98, 81-451, Gdynia, Poland > Phone: +48 58 782 45 40 / Fax: +48 58 782 45 41 >
