Fredhopper Memory Settings – Rezolve Ai Support Portal

This article will provide further details and guidance for configuring Fredhopper memory settings.

Memory usage of Fredhopper processes can be analyzed using the log/<PROCESS>.gc.log log files. If multiple "Full GC" entries occur in these files the memory assignment needs to be increased usually.

Process	Setting	Default	Tuned	When to change the default	Where	Comment
qserver	Java Heap -Xmx	1500 (megabyte)	Up to 7000 .. 12000 (megabyte)	large number of indexed items more than 5 queries per second	`qserver_memory` setting
	Stack size	(system dependent)	4m	large number (>500) of facets	-Xss setting	Only needed on Business Manager qserver
treebuilder	Java Heap -Xmx	1200 (megabyte)	Up to 3000 .. 5000 (megabyte)	large number of indexed attributes (> 200)	`treebuilder_memory` setting
searchindexer	Java Heap -Xmx	900 (megabyte)	Up to 2000 .. 5000 (megabyte)	large number of locales large number of primary items	`searchindexer_memory` setting
xmlloader	Java Heap -Xmx	400 (megabyte)	Up to 1000 .. 5000 (megabyte)	large number of attributes more than 1Mio items set/list attributes with many values	`xmlloader_memory` setting
syncserver	Java Heap -Xmx	180 (megabyte)	Up to 250 (megabyte)	more than 5 live instances	`syncserver_memory` setting
syncclient	Java Heap -Xmx	60 (megabyte)		Should not be needed	`syncclient_memory` setting
ETL	Java Heap -Xmx	4000 (megabyte)	Up to 7000 (megabyte)	Large lists to sort	`kitchen_memory` setting