Project

General

Profile

Feature #1785

Expend ORM instance, live cache via Redis

Added by Tab Tu 10 months ago. Updated 10 months ago.

Status:
Closed
Priority:
Normal
Start date:
2024-05-26
Due date:
2024-07-31
% Done:

100%

Estimated time:
(Total: 0.00 h)

Description

ORM for property searching becomes to legacy due to the tech stack upgrading. It is limitated at the memory size on server (VM). Multiple singlton instances won't be able to support the increated data in VOW.

Before 2022, the maximum live listing number is 70k in Jul/Aug, but now we are facing 100k available properties to be addressed onto memory whcih takes over 6GB or even more. Consider to use Redis for a better solution on performance searching.

Involve cache to solve the over sea request with a better performance. Load-balance is considerable.

We have some out dated servers which can be set as cache services.


Subtasks

Feature #1800: Build redis instance at localClosedJennifer Jiang2024-05-262024-05-31

Actions
Task #1801: Create VOW listing topics on redisClosedJennifer Jiang2024-05-312024-06-05

Actions
Task #1802: Update VOW cache to available listings onlyClosedJennifer Jiang2024-06-012024-06-04

Actions
Feature #1803: Migrate VOW recent 6 month SOLD data into cacheClosedJennifer Jiang2024-06-112024-06-27

Actions
Feature #1804: Migrate IDX/DDF into cacheClosedJennifer Jiang2024-06-242024-06-30

Actions
Feature #1805: Cache managementClosedJennifer Jiang2024-06-302024-07-25

Actions
Feature #1806: Test querying from cacheClosedJennifer Jiang2024-07-072024-07-31

Actions

No data to display

Also available in: Atom PDF