Releases: LD4P/qa_server
v7.5.0
- UI improvements of check_status page
- pre-populate selection fields with most recently submitted authorities
- add ability to compare two authorities' accuracy tests in UI
- update check_status UI to require GO button click to start processing
- fix javascript to avoid referencing missing elements
- accuracy test updates
- accuracy tests default to
context=false
since it is not required for testing - allow accuracy tests through rspec to be marked pending (allows for better regression testing)
- add pending to failing validation tests such that accuracy_spec passes
- sync tests with production accuracy tests
- fix typo in
position
and a few syntax errors - adjust result_size for validations where passing tests return less than 200 chars
- split locnames_rwo_ld4l_cache into 3 sets of tests of about 9 each to avoid time out
- add extended context for getty_aat_ld4l_cache and getty_tgn_ld4l_cache
- add authority locvocabs_ld4l_cache
- accuracy tests default to
- add request_data to status_logger (e.g. query for search, identifier for term)
- update to latest bixby v3.0
v7.4.0
Change Log
- add size and complexity performance statistics (not auto-generated)
Usage
$ bundle exec rails console
> cr = { AGROVOC_LD4L_CACHE: 3, CERL_LD4L_CACHE: 37, DBPEDIA_LD4L_CACHE: 0, GEONAMES_LD4L_CACHE: 11, ... }
> QaServer::PerformancePerByteJob.perform_now(authority_complexity_ratings: cr)
Generates log/performance.csv
with the following stats:
- authority_name
- complexity_rating
- action
- size_bytes
- retrieve_bytes_per_ms
- graph_load_bytes_per_ms
- normalize_bytes_per_ms
- retrieve_ms_per_byte
- graph_load_ms_per_byte
- normalize_ms_per_byte
v7.3.0
Description
Move generation of graphs to background jobs. This impacts generation of...
- Historical Summary Graph
- Performance Year Graphs
- Performance Month Graphs
- Performance Day Graphs
No special actions required. You can monitor background processes related to the monitor status page in log/monitor.log
.
v7.2.1
v7.2.0
Actions Required to Upgrade
Update to qa_server v7.2.0 and run bundle install.
bundle update qa_server
Changes
This release moves the generated charts for the monitor status page from /app/assets/images/charts
to /public/qa_server/charts
. It is more common for generated and uploaded files to go into the public directory.
Change Log
- move generated monitor status graphs from assets to public directory
v7.1.3
v7.1.2
v7.1.1
v7.1.0
Actions Required to Upgrade
Complete the v7.0.0 refactor by moving the generation of the history graph to app/cache_processors
directory. It also adds the ability to set the max size of the performance cache via an environment variable.
See change log for a list of changes.
Update to qa_server v7.1.0 and run bundle install.
bundle update qa_server
Setting max size for performance cache
The max size of the performance cache can now be set by environment variable ENV['MAX_PERFORMANCE_CACHE_SIZE'] = "16 MB"
or through the qa_server initializer max_performance_cache_size = 8.megabytes
. The default if no value is set is 32.megabytes
.
Change Log
- allow performance cache size to be set by environment variable
- move generation of history graph to cache_processors
- log warning in monitor logger if graphs fail to create
- monitor_status page won't try to display graphs if graph file does not exist
v7.0.0
Actions Required to Upgrade
This release does a major refactor of the caching system used to improve performance of the Monitor Status page. It greatly simplifies and consolidates the location of the caching code into the app/cache_processors
directory. The relocation of classes created the need for a change in the major version.
Update to qa_server v7.0.0 and run bundle install.
bundle update qa_server
Changes
This is a refactoring of code. It improves the loading performance of the Monitor Status page. It does not effect the functioning of search and fetch actions.
This release includes changes of the output to the monitor log. Actions are now only recorded once during a load of the Monitor Status page. Previously, the same message could appear multiple times. The messages themselves have been simplified to make the log easier to read.
Change Log
- refactor of caching system to simplify the process
- rename monitor_cache_service to cache_expiry_service
- move generation of hourly graph to cache_processors
- move generation of daily and monthly graphs to cache_processors
- move performance datatable cache control to cache_processors
- move caching of summary and historical data to cache_processors
- move caching of test execution marker to cache_processors
- move performance cache of performance data to cache_processors