Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move virtuoso.ini files to seperate config folder #209

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

elpoelma
Copy link
Contributor

@elpoelma elpoelma commented Oct 29, 2024

Overview

This PR makes some adjustments to the virtuoso.ini files and where they are stored.
This PR stores the .ini files in /config/virtuoso. This approach is similar to the ones taken by https://github.com/lblod/app-lokaal-mandatenbeheer and https://github.com/lblod/app-digitaal-loket.

This PR also introduces seperate virtuoso.ini files for:

  • Local use
  • DEV/QA
  • Production

Finally, this PR also adjusts some parameters of the .ini files, mostly in terms of maximum memory usage.

Tracking the .ini files for DEV/QA and production allows us to easily tweak the parameters.

@elpoelma elpoelma self-assigned this Oct 29, 2024
@elpoelma elpoelma changed the title Move virtuoso.ini files to seperate config folder Move virtuoso.ini files to seperate config folder Oct 29, 2024
;; Uncomment next two lines if there is 8 GB system memory free
;NumberOfBuffers = 680000
;MaxDirtyBuffers = 500000
NumberOfBuffers = 680000
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why do we have 4G but we have uncommented the lines for 8gb of free memory?

[TempDatabase]
DatabaseFile = /usr/local/virtuoso-opensource/var/lib/virtuoso/db/virtuoso-temp.db
TransactionFile = /usr/local/virtuoso-opensource/var/lib/virtuoso/db/virtuoso-temp.trx
MaxCheckpointRemap = 000
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's not clear to me why this is 0 or what that means in practice. In QA it's 2000.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure either. I left the production config (taken from the prod server) unchanged, as I don't really understand all the parameters.

MaxQueryMem = 4G ; memory allocated to query processor ;;Niels said to 4g
VectorSize = 1000 ; initial parallel query vector (array of query operations) size
MaxVectorSize = 1000000 ; query vector size threshold.
AdjustVectorSize = 0
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This being 0 here and 1 on production could cause differences in behaviour between them, I'm not familiar enough with these settings to know whether that's an issue.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same comment as above. I'm also not familiar enough, so I left these settings unchanged.

@@ -62,6 +62,7 @@ services:
DEFAULT_GRAPH: "http://mu.semte.ch/application"
volumes:
- ./data/db:/data
- ./config/virtuoso/virtuoso.ini:/data/virtuoso.ini # Note: on production override this setting
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As far as my thinking goes, the docker-compose.yml file should be the production version. The .dev.yml should include the version for development (mapping the same internal path means that the latest mapping wins).

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's also fair! I mainly based this approach/config on the one of LMB and Loket, to maintain a bit of consistency.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants