Performance issue when using multiple map blocks

[RogueVortex]

Hello,

Thank you very much for your extension — it’s been incredibly helpful in solving many of my tasks.

As part of my work, I need to insert 5 to 10 map blocks on a single wiki page, each displaying different markers. However, with this setup, the pages load very slowly for logged-in users.

Could you please advise on how this can be optimized? What direction should I explore to improve performance?

I would really appreciate any suggestions.

[JeroenDeDauw]

Is the slowness only for logged-in users?

What kind of maps are you embedding? Is there a lot of data shown on them? Where does this data come from?

[RogueVortex]

Yes, the pages load slowly only for registered users. For unregistered users, they load instantly — most likely because I'm using HtmlCache, which serves them immediately.

I embed the maps using blocks like these:

{{#display_map: 
|layer = my_layer
|geojson = my_page/my_layer
|zoom = 3
|enablefullscreen = yes
|icon = marker.png
}}

I add the layers using the following structure in leaflet-providers.js:

'my_layer': {
	url: '/maps/my_layer/{z}-{x}-{y}.jpg',
	options: {	
		minZoom: 1,
		maxZoom: 5,				
		attribution: 'my_layer',
		noWrap: true,
		bounds: [[90, -180], [-90, 180]] 
	}
}

[JeroenDeDauw]

The layers are unlikley to be the issue but the GeoJSON might well be. Are you referencing GeoJSON files or wiki pages? And how big are the files/pages?

If my guess here is correct, then I don't know how to improve the performance besides ensuring the page does not need to be re-rendered on view. Did you disable the parser cache for logged in users?

[RogueVortex]

I extract GeoJSON data from pages. Some pages contain a large number of markers (hundreds), while others have just a few (1–2 markers). However, based on my experiments, the issue is not the amount of data, but rather the number of map blocks and how the server renders the page. When there are many such blocks, the server-side rendering becomes very slow.

For now, I’ve solved the problem by generating maps via an ask query using a template, and applying the @deferred parameter — this way, the page loads instantly, and the maps are loaded afterward.

[RogueVortex]

My current caching settings are as follows:

## Shared memory settings
$wgMainCacheType = CACHE_MEMCACHED;
$wgMemCachedServers = [ '127.0.0.1:11211' ];

$wgParserCacheType = CACHE_MEMCACHED;
$wgMessageCacheType = CACHE_MEMCACHED; 
$wgSessionCacheType = CACHE_MEMCACHED;

$wgUseFileCache = true;
$wgFileCacheDirectory = "my/path";
$wgFileCacheDepth = 2;

$smwgMainCacheType = CACHE_MEMCACHED;
$smwgValueLookupCacheType = CACHE_MEMCACHED;
$smwgQueryResultCacheType = CACHE_MEMCACHED;
$smwgQueryResultCacheLifetime = 60 * 60 * 24 * 7;
$smwgEnabledQueryDependencyLinksStore = true; 
$smwgQueryResultNonEmbeddedCacheLifetime = 60 * 60;