Moving Only the Web Server Closer to Users Slowed Page Loads, Measurements Show

·4 views

A production e-commerce site on EC-CUBE faced a request to host its server in Japan, since its users are there. However, the managed database remained in Seoul, so moving only the web server would separate it from the database. Earlier, a dev server in Tokyo connecting to the Seoul database ran about four times slower than production, and TCP connection tests confirmed the cross-region gap: 4–9ms within Seoul versus 37–42ms from Tokyo. Because the framework issues dozens to a hundred queries per page, that delay multiplies into seconds of extra load time. The team kept the existing setup, and an unused 1GB database found in Tokyo was flagged for deletion after code and config checks found no references.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

OpenAI doubles ChatGPT Pro usage limits and merges ChatGPT and Codex allowances

OpenAI has confirmed it is doubling usage limits for its Pro plan, according to BleepingComputer. The company is also bringing ChatGPT Work capabilities directly into regular Chat. Usage allowances across ChatGPT and Codex are being combined, though reporting suggests a shared pool but does not confirm how it is calculated. Details such as the baseline limits, which plans beyond Pro are affected, and the rollout timeline were not disclosed in the available coverage. Users are advised to consult OpenAI's official announcement for exact figures and schedules.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Rotifer v0.9.4 gives AI agents persistent memory across runs

Previously, each run of a Rotifer gene started with no memory of earlier runs. Version 0.9.4 of the protocol lets every agent keep memory that its genes can read and write between runs through four calls. Memory is owned by the agent rather than by individual genes, so replacing or upgrading a gene does not erase what the agent has learned. Entries fall into four categories (PREFERENCE, PATTERN, CONTEXT, CACHE), each with its own eviction behavior, and each agent has a default quota of 10 MB that can be set when it is created. Access rules, optional retention limits, and operator tools for listing and deleting entries govern how the stored memory is used and controlled.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Google Extends UGC Spam Guidance to Publishing and Sharing Tools

Google has broadened its guidance on user-generated content abuse to cover platforms and apps that let people publish shared pages, generated content, or web apps. The focus is on the indexing and abuse controls of third-party publishing and sharing services, not only traditional forums and comment sections. The guidance, last updated October 26, 2026, recommends that platform owners index only content intended for Search, using noindex meta tags, X-Robots-Tag headers, or robots.txt blocking. It also urges operators to monitor for abuse signals, such as sudden surges in new indexed URLs, and to verify their sites in Search Console.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Researchers urge Gibbon school software deployments to separate student records from public login pages

A security-focused article argues that Gibbon, an open-source school management platform covering student profiles, attendance, and enrolment, should keep sensitive school data distinct from its publicly visible login or admissions pages. It notes that search-engine queries found 872 hosts matching the application name and 632 matching its title, though a name match alone does not show that records are exposed. The piece emphasizes reviewing permissions for each role such as administrators, teachers, parents, and support staff, especially for impersonation, messaging, and medical or safeguarding fields. It also recommends verifying OAuth2 login behavior, ensuring external identities do not automatically receive administrator rights, and testing session expiry and account deactivation. Its closing guidance is that organizations should confirm host ownership and monitor authentication and permission events rather than act on version-based assumptions.

0 comments Read more at DEV Community