Setting up initial cache before starting the server
See original GitHub issueI just started deploying an universal app using these tools.
I’ve noticed that the first request after I deploy is really slow, then subsequent requests are fast.
From this: https://github.com/halt-hammerzeit/webpack-isomorphic-tools/issues/17 I’m guessing it has to do with building that initial cache. Is there a way I can trigger building this before the server starts?
I’m using these tools via:
var WebpackIsomorphicTools = require('webpack-isomorphic-tools');
global.webpackIsomorphicTools = new WebpackIsomorphicTools(require('../webpack/webpack-isomorphic-tools'))
.development(__LOCAL__)
.server(rootDir, function() {
require('../src/server');
});
Issue Analytics
- State:
- Created 8 years ago
- Reactions:1
- Comments:10 (6 by maintainers)
Top Results From Across the Web
Configuring initial spec cache loading during server startup
Configuring initial spec cache loading during server startup. Product Master provides a mechanism to populate the spec cache during service startup.
Read more >5 Initial Setup and Configuration - Oracle Help Center
This chapter describes the steps to initially configure Oracle Web Cache to begin caching application Web server content after installation.
Read more >Installing Cache Server - NetBrain
Complete the following steps with administrative privileges. 1.Obtain the installation package of Cache Server from NetBrain and save it in your local folder....
Read more >Caching configuration best practices | Fastly Help Guides
Integrate Fastly with your application platform · Check your cache hit ratio · Set a fallback TTL · Understand how cache control headers...
Read more >Start Cache using Web Manager and PowerShell - Alachisoft
In the left navigation bar, click on Clustered Caches or Local Caches, based on the cache server to start. Against the cache name,...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
There’s no migration since these aren’t two different major versions of a single tools but rather two completely different tools. Start from scratch.
Thanks! Am I understanding correctly that
unversal-webpack
would solve issue of slow initial cache since it’s making pre-build of assets?