Sharing practical vivo Internet technology insights and salon events, plus the latest industry news and hot conferences.
vivo migrated five 20‑TB MySQL clusters to OceanBase using OCP, oblogproxy, and OMS, eliminating sharding costs, achieving over 70% storage savings, improving consistency and performance, and leveraging native distributed architecture, tenant isolation, and strong compression to support scalable, reliable operations.
Distributed locks synchronize multiple services across nodes, and can be implemented using Redis’s fast, AP‑oriented SET‑NX with automatic TTL renewal or Zookeeper’s CP‑oriented ephemeral sequential nodes, each offering distinct trade‑offs in performance, consistency, and suitability for various workload requirements.
The article details vivo’s enterprise cloud disk, describing its personal, team, and backup spaces, user authentication via asymmetric encryption and SSO, metadata storage in MySQL with object storage for files, and the implementation of file operations—including permission management, partner access, and both small‑file and multipart large‑file upload workflows.
Ke Jie explains why reducing the Game Center APK—by eliminating alpha‑PNG images, unused code and resources, limiting language and density assets, disabling v1 signing, compressing images, loading native libraries on demand, shipping only 64‑bit binaries, enabling code/resource shrinking and R‑file inlining—cut size by about 31% (≈20 MB), boosting download conversion and launch performance.
The article examines a real‑world memory alarm in a Vivo service, explains how glibc’s ptmalloc allocator manages heap memory via brk, sbrk, and mmap, shows why freed chunks stay in bins, and recommends limiting heap growth or switching to jemalloc for faster reclamation.
At the 19th China Linux Kernel Developer Conference, vivo unveiled nine open‑source innovations—including DMA‑BUF DIO for AI model loading, ZHP memory compression, EROFS and f2fs filesystem enhancements, and I/O optimizations—contributing significant performance gains and demonstrating its commitment to Linux kernel advancement worldwide.
This guide explains how to diagnose and fix TiKV disk‑space problems by identifying oversized log files, redundant space‑placeholder files, and excessive RocksDB/Titan data, offering command‑line checks, configuration tweaks such as enabling log rotation, disabling reserve space, and tuning GC and Titan discardable‑ratio to restore balanced storage.
Technical debt, introduced by Ward Cunningham, describes the hidden cost of rushed or sub‑optimal code that degrades efficiency, quality, and developer experience; it arises from intentional or unintentional shortcuts across four dimensions, and can be managed through systematic identification, analysis, resolution, review, and dedicated ownership, yielding more stable, higher‑quality software.
This article presents a Sentinel‑based dynamic rate‑limiting solution that uses parameter priority and a sliding‑window counter to automatically adjust thresholds per scenario, addressing the limitations of static QPS limits, simplifying rule management via Zookeeper, and integrating as an independent SDK within Sentinel’s responsibility‑chain architecture.
To simplify large‑scale Vue upgrades such as Vue 2→Vue 3, Webpack 4→Webpack 5, or migration to Vite, the author presents an automated AST‑based migration scaffold that parses JavaScript, Vue, and style files, applies transformation rules with GoGoCode and PostCSS, and rewrites code, reducing manual effort and error risk.
