dedicated Agent Totals calculation hardware to optimize darwin

A New Way to calculate Agent Totals keeps Darwin.Cloud Efficient and Responsive

In the fast-paced world of real estate, timing and accuracy are everything. darwin.Cloud is always evolving to ensure its tools work as smoothly as possible. Recently, we’ve made a change to how we calculate agent performance data (aka Agent Totals), and it’s a game-changer.

/files/AgentTotals.png{/content:image}

When agents sell properties, darwin.Cloud calculates important totals—like how many homes they’ve sold and how much commission they’ve earned. We call these calculations "Agent Totals". These numbers are key for reports, email campaigns, commission calculations and tracking success. Until now, our main system handled these calculations while also managing all the other tasks that keep darwin.Cloud running. This could sometimes slow things down.

Here’s what’s new: we’ve set up a separate, dedicated server just for these calculations. Think of it as hiring a specialist to handle one big job instead of juggling it with everything else.

Why Is This Better?

  • Faster Calculations: The new server uses advanced tools to work on many calculations at once, so totals are updated in record time.
  • A More Focused System: By moving the heavy lifting off the main system, we’ve made sure the rest of darwin.Cloud runs faster and more reliably.
  • Timely Data: Because the new server works so quickly, you’ll always have the latest information at your fingertips for reports, spotlights or email campaigns.
  • Room to Grow: As more agents join darwin.Cloud, this setup can easily scale up to handle the load.

This improvement means darwin.Cloud is now even more powerful, helping you stay ahead in the competitive real estate market. Your tools are faster, your data is fresher, and your experience is smoother. That’s progress in action!

Technical Analysis of the Approach

Technical Perspective

  1. Separation of Concerns: By moving the calculation of agent totals to a dedicated server, darwin.Cloud production server can focus solely on its core functionalities without being burdened by these intensive calculations.
  2. Improved Performance:
    • Multi-threading via Kafka: This enables concurrent processing of updates, reducing the time needed to calculate and save totals.
    • Dedicated Resources: The new server exclusively handles these calculations, ensuring consistent performance and avoiding competition for CPU and memory with other processes running on productions servers or primary API servers.
  3. Reduced Production Server Load: Freeing up the production SQL server's resources allows it to better handle real-time API requests and other application-critical tasks.
  4. Scalability: This architecture is scalable. If transaction volumes increase, you can enhance the capacity of the dedicated server or add more Kafka consumers.
  5. Data Timeliness: Calculations are completed faster, ensuring that reporting and marketing teams have access to up-to-date data.