Releases: restarone/violet_rails
0.9.117
What's Changed
Full Changelog: 0.9.116...0.9.117
0.9.116
What's Changed
- [feature] include geolocation in cookies metadata hash by @alis-khadka in #1564
Addresses: #1559
Screen.Recording.2023-05-23.at.8.32.06.PM.mov
Full Changelog: 0.9.115...0.9.116
0.9.115
What's Changed
- [feature] API Namespace Associations by @Pralish
- update README by @guspan-tanadi
Full Changelog: 0.9.114...0.9.115
0.9.114
0.9.113
What's Changed
- [plugin] for sending report of billables by @alis-khadka in #1543
[plugin] for sending report of billables
Addresses: #1517
DEMO
Screen.Recording.2023-04-18.at.6.48.06.PM.mov
Plugin development guide
Full Changelog: 0.9.112...0.9.113
0.9.112
What's Changed
Addresses: #1503
Before
When you had a big API Namespace it would break the view:
After
VIdeo demo
api-namespaces-list-view.mp4
Full Changelog: 0.9.111...0.9.112
0.9.111
What's Changed
- [Bug Fix] PG::DivisionByZero error in analytics v2 by @alis-khadka in #1529
Addresses: #1524
Full Changelog: 0.9.110...0.9.111
0.9.110
What's Changed
- [fix] optimize analytics V2 further + lockdown profiler by @alis-khadka in #1523
Profiling Results 📈 🧪
Slight improvements to user experience
When analysis going back 1 year is shown, there is a noticeable performance improvement:
Less memory & objects used
When a 1 year analysis is shown, less memory and objects are allocated and retained:
Garbage collector is running consistently
on a per request basis, we observe that the garbage collector runs before the request is served. Indicating that used memory has been drained and freed to be used for other requests.
Case study: Marked Restaurant
Resource usage
comparison of memory / CPU usage before and after patch
Baseline 🆎
The "resting memory rate" for a high traffic Violet system is around 600MB:
Before ⏪
Viewing the 1 year analysis:
Viewing the 1 month analysis:
We observe 1.2 GB of memory use (double the resting rate)
Profiler result 📈
While attempting to run the memory profiler on the 1 year analysis, we observed 3GB+ of memory usage
⭐ After the test was run, puma was restarted to ensure system stability
After ⏩
We observe 720MB of memory use
We observe 850 MB of memory use
Profiler result 📈
We observe 900MB of memory use when profiling the 1 year analysis
Result
The system is now consuming memory in analytics V2 comparable to its resting memory usage rate.
Full Changelog: 0.9.109...0.9.110
0.9.109
What's Changed
- [feature] install strong_migrations by @Pralish in #1514
- [housekeeping] update contribution guide by @donrestarone
🦾 Strong Migrations 💾
Data consistency, durability and availability is important. Which is why now, we are enforcing database migration standards via strong_migrations
: https://github.com/ankane/strong_migrations -- to preserve the uptime of your system and encourage zero-downtime data/schema migrations.
Full Changelog: 0.9.108...0.9.109