PHPMem v2.0.1

Version
1.6.45
Uptime
18 days 6 hours 31 minutes 10 seconds

Memory

Total
512MB
Used
12,33MB (2.41%)
Free
499,67MB

Keys

Current
13 424
Total (since start)
40 994
Evictions
0
Reclaimed
762
Expired Unfetched
0
Evicted Unfetched
0

Connections

Current
4 / 1 024 max
Total
244 861
Rejected
0
llm:4c5bbc3e556f02da00df5c7aeb3d59987ea3581a40ddfa990e1e96124943141c
TTL 3 days 21 hours 39 minutes 35 seconds Size 1,53KB Export
Edit
{
    "action": "final",
    "content": "**Short answer: no true duplicates, but there is a small pattern of near-duplicates worth knowing about.**\n\nFrom the duplicate check I ran over `raw.semi_conductor_se` (422,729 rows):\n\n- **Exact duplicates: 0.** No group of rows repeats across all the data columns (`exact_dup_groups` = 0).\n- **Key duplicates: 0.** The stated grain is one row per stock per trading day. `dup_key_groups` = 0, and `dup_company_date_groups` = 0, so no company/date combination appears more than once.\n- **Row identifiers are unique.** `_unnamed_0` has 422,729 distinct values, equal to the total row count, so no row ID is reused.\n- **Near-duplicates: 647 groups** (`same_values_diff_date_groups`). These are cases where the same price and volume values show up on different dates for the same stock. They are not duplicated records, because the dates differ. The most likely explanation is an unchanged quote carried forward, such as a halted or illiquid stock, or a data-fill artifact. I have not examined these groups individually, so I can't say which explanation applies. Against 422,729 rows this is a very small share.\n\n**Implication:** no de-duplication is needed before analysis. If you are computing returns or volatility, the 647 repeated-value groups could produce zero-change days. It would be worth inspecting them for the affected companies, especially any with zero volume, before relying on them."
}