Curabitur aliquam euismod dolor non ornare

26. travnja 2026. u 02:15:47 Carol Williams

Understanding the Problem

When building modern web applications, performance is not just a feature — it's a requirement. Users expect sub-second response times, and search engines penalize slow pages. This post explores practical techniques for optimization.

Key Metrics

Time to First Byte (TTFB)
Largest Contentful Paint (LCP)
Cumulative Layout Shift (CLS)

"Premature optimization is the root of all evil" — Donald Knuth

However, measured optimization based on profiling data is the root of all performance gains. Let's look at real-world examples.

Database Optimization

-- Before: full table scan
SELECT * FROM posts WHERE status = 'published' ORDER BY created_at DESC;

-- After: indexed query with pagination
SELECT id, title, summary FROM posts
WHERE status = 'published'
ORDER BY created_at DESC
LIMIT 20 OFFSET 0;

The difference? From 850ms to 12ms on a table with 500K rows.

Caching Strategy

Use a multi-layer cache:

L1: In-memory (APCu) — microsecond access
L2: Redis — millisecond access
L3: Database — last resort

Each layer has different TTLs and invalidation strategies.

beginner consectetur devops patterns

Prijavi se u svrhu objave komentara

2 komentara

Tom Doe komentirao dana 26. tra 2026. 20:21

Mauris dapibus risus quis suscipit vulputate. Nunc viverra elit ac laoreet suscipit. Pellentesque et sapien pulvinar consectetur. Era brevis ratione est. Diatrias tolerare tanquam noster caesium. Ubi est audax amicitia. Morbi tempus commodo mattis.

Bob Johnson komentirao dana 26. tra 2026. 20:20

Lorem ipsum dolor sit amet consectetur adipiscing elit. Ubi est audax amicitia. Diatrias tolerare tanquam noster caesium. Vae humani generis. Eros diam egestas libero eu vulputate risus. Bassus fatalis classiss virtualiter transferre de flavum. Sunt torquises imitari velox mirabilis medicinaes. Teres talis saepe tractare de camerarius flavum sensorem.

Ovo je demo web aplikacija napravljena unutar Symfony okvirne tehnologije, služi kako bi pokazala preporučeni način korištenja Symfony okvirne tehnologije.

Za više informacija, provjerite Symfony dokumentaciju.

Klikni na ovaj gumb kako bi pokazali izvorni kod od Kontrolora i Predloška korištenog prilikom stvaranja ove stranice.

src/Controller/BlogController.php at line 272

/**
 * NOTE: when the controller argument is a Doctrine entity, Symfony makes an
 * automatic database query to fetch it based on the value of the route parameters.
 * The '{slug:post}' configuration tells Symfony to use the 'slug' route
 * parameter in the database query that fetches the entity of the $post argument.
 * This is mostly useful when the route has multiple parameters and the controller
 * also has multiple arguments.
 * See https://symfony.com/doc/current/doctrine.html#automatically-fetching-objects-entityvalueresolver.
 */
#[Route('/posts/{slug:post}', name: 'blog_post', requirements: ['slug' => Requirement::ASCII_SLUG], methods: ['GET'])]
public function postShow(Post $post): Response
{
    // Symfony's 'dump()' function is an improved version of PHP's 'var_dump()' but
    // it's not available in the 'prod' environment to prevent leaking sensitive information.
    // It can be used both in PHP files and Twig templates, but it requires to
    // have enabled the DebugBundle. Uncomment the following line to see it in action:
    //
    // dump($post, $this->getUser(), new \DateTime());
    //
    // The result will be displayed either in the Symfony Profiler or in the stream output.
    // See https://symfony.com/doc/current/profiler.html
    // See https://symfony.com/doc/current/templates.html#the-dump-twig-utilities
    //
    // You can also leverage Symfony's 'dd()' function that dumps and
    // stops the execution

    return $this->render('blog/post_show.html.twig', ['post' => $post]);
}

templates/blog/post_show.html.twig at line 1

RSS Blog Članaka