37 posts
discord Here's the Discord Changelog from March 24, 2026. You can also find the most recent Changelog in the Discord app under Settings > What's New. With everyone finally settled in after coming back from end-of-year breaks, you’re likely getting back into your usual routines for vibin…
meta Meta recognizes the long-term benefits of jemalloc, a high-performance memory allocator, in its software infrastructure. We are renewing focus on jemalloc, aiming to reduce maintenance needs and modernize the codebase while continuing to evolve the allocator to adapt to the late…
discord Discord has introduced its "Patch Notes" series to document ongoing improvements in performance, reliability, and general system responsiveness. The initiative emphasizes a transparent development cycle where community feedback directly informs engineering priorities and bug-squishing efforts. **User-Driven Bug Tracking** * Engineers actively monitor a Bimonthly Bug Megathread on the community-managed r/DiscordApp subreddit. * This collaborative approach allows the development team to identify and address user-reported friction points that may not be caught during internal testing. **Beta Testing via TestFlight** * iOS users can opt into a TestFlight version of the application to test upcoming features and early builds before they are released to the general public. * This program serves as a critical frontline for identifying edge-case bugs and ensuring stability across the mobile ecosystem. **Deployment and Rollout Procedures** * All documented fixes in the series have been officially committed and merged into the codebase. * Changes are distributed through a rolling deployment, which means updates may arrive on individual platforms at different times depending on the release schedule. To ensure the best user experience and contribute to the platform's stability, users are encouraged to participate in the TestFlight program or report specific technical issues through the designated community channels.
naver The development of `@RequestCache` addresses the performance degradation and network overhead caused by redundant external API calls or repetitive computations within a single HTTP request. By implementing a custom Spring-based annotation, developers can ensure that specific data is fetched only once per request and shared across different service layers. This approach provides a more elegant and maintainable solution than manual parameter passing or struggling with the limitations of global caching strategies. ### Addressing Redundant Operations in Web Services * Modern web architectures often involve multiple internal services (e.g., Order, Payment, and Notification) that independently request the same data, such as a user profile. * These redundant calls increase response times, put unnecessary load on external servers, and waste system resources. * `@RequestCache` provides a declarative way to cache method results within the scope of a single HTTP request, ensuring the actual logic or API call is executed only once. ### Limitations of Manual Data Passing * The common alternative of passing response objects as method parameters leads to "parameter drilling," where intermediate service layers must accept data they do not use just to pass it to a deeper layer. * In the "Strategy Pattern," adding a new data dependency to an interface forces every implementation to change, even those that have no use for the new parameter, which violates clean architecture principles. * Manual passing makes method signatures brittle and increases the complexity of refactoring as the call stack grows. ### The TTL Dilemma in Traditional Caching * Using Redis or a local cache with Time-To-Live (TTL) settings is often insufficient for request-level isolation. * If the TTL is set too short, the cache might expire before a long-running request finishes, leading to the very redundant calls the system was trying to avoid. * If the TTL is too long, the cache persists across different HTTP requests, which is logically incorrect for data that should be fresh for every new user interaction. ### Leveraging Spring’s Request Scope and Proxy Mechanism * The implementation utilizes Spring’s `@RequestScope` to manage the cache lifecycle, ensuring that data is automatically cleared when the request ends. * Under the hood, `@RequestScope` uses a Singleton Proxy that delegates calls to a specific instance stored in the `RequestContextHolder` for the current thread. * The cache relies on `RequestAttribute`, which uses `ThreadLocal` storage to guarantee isolation between different concurrent requests. * Lifecycle management is handled by Spring’s `FrameworkServlet`, which prevents memory leaks by automatically cleaning up request attributes after the response is sent. For applications dealing with deep call stacks or complex service interactions, a request-scoped caching annotation provides a robust way to optimize performance without sacrificing code readability. This mechanism is particularly recommended when the same data is needed across unrelated service boundaries within a single transaction, ensuring consistency and efficiency throughout the request lifecycle.
naver JVM applications often suffer from initial latency spikes because the Just-In-Time (JIT) compiler requires a "warm-up" period to optimize frequently executed code into machine language. While traditional strategies rely on simulated API calls to trigger this optimization, these methods often introduce side effects like data pollution, log noise, and increased maintenance overhead. This new approach advocates for a library-centric warm-up that targets core execution paths and dependencies directly, ensuring high performance from the first real request without the risks of full-scale API simulation. ### Limitations of Traditional API-Based Warm-up * **Data and State Pollution:** Simulated API calls can inadvertently trigger database writes, send notifications, or pollute analytics data, requiring complex logic to bypass these side effects. * **Maintenance Burden:** As business logic and API signatures change, developers must constantly update the warm-up scripts or "dummy" requests to match the current application state. * **Operational Risk:** Relying on external dependencies or complex internal services during the warm-up phase can lead to deployment failures if the mock environment is not perfectly aligned with production. ### The Library-Centric Warm-up Strategy * **Targeted Optimization:** Instead of hitting the entry-point controllers, the focus shifts to warming up heavy third-party libraries and internal utility classes (e.g., JSON parsers, encryption modules, and DB drivers). * **Internal Execution Path:** By directly invoking methods within the application's service or infrastructure layer during the startup phase, the JIT compiler can reach "Tier 4" (C2) optimization for critical code blocks. * **Decoupled Logic:** Because the warm-up targets underlying libraries rather than specific business endpoints, the logic remains stable even when the high-level API changes. ### Implementation and Performance Verification * **Reflection and Hooks:** The implementation uses application startup hooks to execute intensive code paths, ensuring the JVM is "hot" before the load balancer begins directing traffic to the instance. * **JIT Compilation Monitoring:** Success is measured by tracking the number of JIT-compiled methods and the time taken to reach a stable state, specifically targeting the reduction of "cold" execution time. * **Latency Improvements:** Empirical data shows a significant reduction in P99 latency during the first few minutes of deployment, as the most CPU-intensive library functions are already pre-optimized. ### Advantages and Practical Constraints * **Safer Deployments:** Removing the need for simulated network requests makes the deployment process more robust and prevents accidental side effects in downstream systems. * **Granular Control:** Developers can selectively warm up only the most performance-sensitive parts of the application, saving startup time compared to a full-system simulation. * **Incomplete Path Coverage:** A primary limitation is that library-only warming may miss specific branch optimizations that occur only during full end-to-end request processing. To achieve the best balance between safety and performance, engineering teams should prioritize warming up shared infrastructure libraries and high-overhead utilities. While it may not cover 100% of the application's execution paths, a library-based approach provides a more maintainable and lower-risk foundation for JVM performance tuning than traditional request-based methods.
discord Discord’s "Patch Notes" series provides a transparent look into the engineering team's ongoing efforts to improve platform performance, reliability, and responsiveness. By focusing on bug-squishing and usability enhancements, the series outlines the specific technical changes implemented to maintain a high-quality user experience across all supported devices. ### Community-Driven Bug Discovery * Discord utilizes the community-run r/DiscordApp subreddit as a primary channel for identifying technical issues. * Users are encouraged to post in the Bimonthly Bug Megathread, which is actively monitored by the engineering team to track and resolve persistent user concerns. * This direct feedback loop allows developers to prioritize fixes that have the most significant impact on the general user base. ### Early Access via iOS TestFlight * For users interested in experimental features, Discord offers an early-access program through Apple’s TestFlight platform. * This beta version allows iOS users to test new updates before they reach the general public, serving as a final stage for identifying "pesky bugs" in a live environment. * Participation in this program provides the engineering team with critical data on feature stability and performance on mobile hardware. ### Commit and Deployment Status * All listed fixes in the series have already been committed and merged into Discord's primary codebase. * Because the deployment process is staged, these updates may roll out to individual platforms and regions at slightly different times even after the notes are published. To ensure the most stable experience and gain access to the latest performance improvements, users should keep their applications updated and consider joining the TestFlight program to help refine upcoming features.
discord Discord’s September 2025 update focuses on enhancing user expression and scaling server infrastructure to unprecedented levels. By introducing massive server capacity increases and highly customizable interface features, the platform aims to better support its largest communities and most active power users. Ultimately, these changes provide a more dynamic social experience through improved profile visibility, expanded pin limits, and flexible multitasking tools. ### Enhanced User Profiles and Multitasking - Desktop profiles now feature a refreshed layout designed to showcase a user's current activities and history more clearly. - Multiple concurrent activities, such as playing a game while listening to music in a voice channel, are now displayed as a "stack of cards" on the profile. - Activities can be moved into a pop-out floating window, allowing users to participate in shared experiences like "Watch Together" while navigating other servers or DMs. - A new audio cue now plays whenever a user turns their camera on to provide immediate feedback that their video stream is live. ### Massive Scaling and Embed Improvements - The default server member cap has been increased to 25 million, supported by engineering optimizations to member list loading speeds for "super-super-large" communities. - The channel pin limit has been expanded fivefold, moving from a 50-message cap to 250 messages per channel. - Native support for AV1 video attachments and embeds was integrated to improve video quality and loading performance. - Tumblr link embeds have been overhauled to include detailed descriptions and metadata for hashtags used in the original post. ### Custom Themes and Aesthetic Upgrades - Nitro users can now create custom gradient themes using up to five different colors, a feature that synchronizes across both desktop and mobile clients. - Two new Server Tag badge packs—the Pet pack and the Flex pack—introduce new iconography for server roles, including animal icons and royalty-themed badges. - Visual updates were made to Group DM icons, which the development team refers to as "facepiles," to better represent groups of friends in the chat list. Users should explore the new custom gradient settings in their Nitro preferences to personalize their workspace and take advantage of the expanded pin limits to better manage information in high-traffic channels.
netflix Netflix has significantly optimized Maestro, its horizontally scalable workflow orchestrator, to meet the evolving demands of low-latency use cases like live events, advertising, and gaming. By redesigning the core engine to transition from a polling-based architecture to a high-performance event-driven model, the team achieved a 100x increase in speed. This evolution reduced workflow overhead from several seconds to mere milliseconds, drastically improving developer productivity and system efficiency. ### Limitations of the Legacy Architecture The original Maestro architecture was built on a three-layer system that, while scalable, introduced significant latency during execution. * **Polling Latency:** The internal flow engine relied on calling execution functions at set intervals, creating a "speedbump" where tasks waited seconds to be picked up by workers. * **Execution Overhead:** The process of translating complex workflow graphs into parallel flows and sequentially chained tasks added internal processing time that hindered sub-hourly and ad-hoc workloads. * **Concurrency Issues:** A lack of strong guarantees from the internal flow engine occasionally led to race conditions, where a single step might be executed by multiple workers simultaneously. ### Transitioning to an Event-Driven Engine To support the highest level of user needs, Netflix replaced the traditional flow engine with a custom, high-performance execution model. * **Direct Dispatching:** The engine moved away from periodic polling in favor of an event-driven mechanism that triggers state transitions instantly. * **State Machine Optimization:** The new design manages the lifecycle of workflows and steps through a more streamlined state machine, ensuring faster transitions between "start," "restart," "stop," and "pause" actions. * **Reduced Data Latency:** The team optimized data access patterns for internal state storage, reducing the time required to write Maestro data to the database during high-volume executions. ### Scalability and Functional Improvements The redesign not only improved speed but also strengthened the engine's ability to handle massive, complex data pipelines. * **Isolation Layers:** The engine maintains strict isolation between the Maestro step runtime (integrated with Spark and Trino) and the underlying execution logic. * **Support for Heterogeneous Workflows:** The supercharged engine continues to support massive workflows with hundreds of thousands of jobs while providing the low latency required for iterative development cycles. * **Reliability Guarantees:** By moving to a more robust internal event bus, the system eliminated the race conditions found in the previous distributed job queue implementation. For organizations managing large-scale Data or ML workflows, moving toward an event-driven orchestration model is essential for supporting sub-hourly execution and low-latency ad-hoc queries. These performance improvements are now available in the Maestro open-source project for wider community adoption.
figma The search for speed in Figma Inside Figma Engineering Quality & performance Infrastructure Behind the scenes
discord Discord's "Patch Notes" series serves as a dedicated update log detailing the platform's ongoing efforts to improve performance, reliability, and responsiveness. By highlighting recent bug fixes and usability enhancements, the series keeps the community informed about the specific engineering changes being deployed across the service. All listed improvements have been officially committed and merged into the codebase, though they may roll out to different platforms at varying speeds. ### Community Feedback and Bug Reporting * Users can report technical issues through the Bimonthly Bug Megathread hosted on the r/DiscordApp subreddit. * This community-run channel allows the Discord Engineering team to directly review and address specific problems reported by the user base. ### Early Feature Testing via TestFlight * iOS users are invited to join the Discord TestFlight program to gain early access to features before their official release. * This beta testing environment is used to identify and "squish" bugs through community interaction before the changes reach the general public. ### Deployment and Release Status * Improvements documented in these updates represent code that has already passed the commit and merge stages of the development cycle. * Because the rollout process is incremental, users may experience a slight delay before specific fixes become active on their particular device or platform. To ensure the best experience, users are encouraged to keep their applications updated and utilize the TestFlight program if they wish to provide early feedback on new builds.
discord Discord's "Patch Notes" series serves as a regular communication channel for documenting technical enhancements across performance, reliability, and platform responsiveness. The initiative emphasizes a collaborative development cycle where engineering fixes are transparently reported alongside invitations for community involvement in the debugging process. ### Community Feedback and Bug Tracking * Discord utilizes the community-managed r/DiscordApp subreddit to gather user feedback on software regressions. * A dedicated Bimonthly Bug Megathread acts as a direct line of communication between the general user base and the engineering team for reporting specific technical issues. ### Pre-release Testing via TestFlight * Users seeking early access to features can participate in the Discord TestFlight program on iOS. * This beta testing phase allows the development team to identify and resolve "pesky bugs" in a controlled environment before the code reaches the stable production branch. ### Deployment and Version Control * All improvements and bug squishing listed in the series represent code that has already been committed and merged into the repository. * Despite being merged, these updates follow a staggered deployment schedule, meaning individual platform availability may vary as the rollout progresses to all users. To help maintain platform stability and gain early access to new functionality, users should consider joining the iOS TestFlight program or documenting persistent issues within the official community Reddit threads.
discord Discord’s Patch Notes series serves as a transparent update log detailing the engineering team's ongoing efforts to enhance performance, reliability, and usability across the platform. By integrating community feedback with rigorous pre-release testing, the company aims to resolve technical debt and refine the user experience through a structured deployment cycle. These updates reflect a commitment to a high-quality, responsive application that evolves based on real-world user interactions. ### Engineering Priorities and Quality Assurance * Focuses on optimizing core application metrics including responsiveness, reliability, and general system performance. * Targets a broad range of improvements from high-level usability features to granular "bug-squishing" and stability fixes. * Ensures that all documented changes have been successfully committed and merged into the codebase prior to announcement. ### Community-Based Bug Identification * Leverages the r/DiscordApp subreddit as a primary channel for crowdsourcing bug reports via a Bimonthly Bug Megathread. * Provides a direct feedback loop where the Engineering team monitors community reports to identify and triage persistent issues. * Encourages user-led troubleshooting to help the development team prioritize fixes that impact the broader user base. ### Pre-Release Testing and Deployment * Utilizes the iOS TestFlight program to allow "edge" users to test upcoming features and identify regressions before they reach the general public. * Directs interested testers to specialized access points like dis.gd/testflight to facilitate early-stage bug detection. * Operates on a rolling deployment schedule, meaning that while fixes are merged, they may appear on different platforms at different times. To help maintain the platform's stability, users are encouraged to report any discovered issues to the community megathread or join the TestFlight program to test new builds before their official release.
figma Speeding up file load times, one page at a time Inside Figma Engineering Quality & performance
discord Discord’s Patch Notes series documents the platform's continuous efforts to improve performance, reliability, and responsiveness through targeted bug fixes and usability enhancements. By integrating community feedback and early-access testing into their development cycle, the engineering team aims to refine the user experience across all supported platforms. ### Community-Driven Bug Reporting * Discord utilizes a Bimonthly Bug Megathread on the community-run r/DiscordApp subreddit to gather reports on persistent issues. * The Engineering team directly monitors these threads to identify, investigate, and resolve bugs reported by the user base. ### iOS TestFlight and Early Access * Users can opt into the Discord TestFlight program on iOS to access and test new features before they are officially released to the general public. * This pre-release environment serves as a critical stage for "squishing" bugs and ensuring feature stability through real-world usage. ### Deployment and Distribution Logistics * All mentioned fixes have been officially committed and merged into the Discord codebase. * Updates are delivered via a staggered rollout, meaning that while the code is finalized, individual users may receive the improvements at different times depending on their platform. To ensure the best possible experience and contribute to the platform's stability, users are encouraged to keep their applications updated and participate in the TestFlight program if they wish to provide early feedback on upcoming builds.
discord Discord’s Patch Notes series serves as a transparent log of the platform's continuous improvements in performance, reliability, and general usability. By combining developer-led bug squishing with direct community feedback, the team aims to deliver a more stable experience across all supported platforms. ### Community-Driven Bug Tracking - Discord leverages the community-run r/DiscordApp subreddit to host a Bimonthly Bug Megathread. - This channel allows users to report specific issues directly to the Engineering team, ensuring that user-facing bugs are identified and prioritized for future sprints. ### Early Access and Beta Testing - iOS users have the option to join Discord’s TestFlight program to test upcoming features before they reach the general public. - This experimental environment allows power users to help "squish" bugs in a live mobile context, providing the engineering team with critical data before a global release. ### Commit and Rollout Procedures - The series clarifies that all listed fixes are officially committed and merged into the codebase. - Because Discord uses a staged rollout system, these changes may take time to propagate to individual platforms and users even after the notes are published. Users looking to contribute to the platform's stability should utilize the dedicated Reddit megathread for bug reporting or join the TestFlight program to provide early feedback on upcoming mobile builds.