Skip to content

Commit b5b0052

Browse files
authored
Update benchmarking.md
1 parent a4cd4d2 commit b5b0052

1 file changed

Lines changed: 6 additions & 4 deletions

File tree

  • content/learning-paths/servers-and-cloud-computing/ruby-on-rails

content/learning-paths/servers-and-cloud-computing/ruby-on-rails/benchmarking.md

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -103,10 +103,12 @@ Results summarized from the your run on the `c4a-standard-4` (4 vCPU, 16 GB memo
103103
| Computation | 0.410907 | 0.000000 | 0.410907 | 0.410919 |
104104

105105

106-
### Analysis of Results
106+
### Key Takeaways
107107

108108
When you look the benchmarking results, you will notice that on the Google Axion C4A Arm-based instances:
109109

110-
- **Database operations are the main bottleneck:** DB Insert and DB Query take the most time.
111-
- **DB Query has the highest latency:** It is the slowest operation at 3.39 seconds.
112-
- **Core computation is fast:** Pure Ruby/Rails calculations complete quickly at 0.41 seconds.
110+
Rails on Arm64 performs consistently: Ruby and PostgreSQL are both natively optimized for Arm, providing stable, predictable latency.
111+
Database I/O remains the main optimization target: Techniques such as query caching, connection pooling, and async queries can improve DB-heavy performance.
112+
Compute-bound tasks scale well: Axion’s Arm cores and Ruby’s YJIT show excellent CPU utilization for non-I/O workloads.
113+
114+
Ruby on Rails runs efficiently on Google Cloud’s Axion-based C4A Arm64 instances.

0 commit comments

Comments
 (0)