{"action":"closed","issue":{"url":"https://api.github.com/repos/epoberezkin/ajv/issues/8","labels_url":"https://api.github.com/repos/epoberezkin/ajv/issues/8/labels{/name}","comments_url":"https://api.github.com/repos/epoberezkin/ajv/issues/8/comments","events_url":"https://api.github.com/repos/epoberezkin/ajv/issues/8/events","html_url":"https://github.com/epoberezkin/ajv/issues/8","id":88379732,"number":8,"title":"Caching limit and strategy","user":{"login":"bugventure","id":649380,"avatar_url":"https://avatars.githubusercontent.com/u/649380?v=3","gravatar_id":"","url":"https://api.github.com/users/bugventure","html_url":"https://github.com/bugventure","followers_url":"https://api.github.com/users/bugventure/followers","following_url":"https://api.github.com/users/bugventure/following{/other_user}","gists_url":"https://api.github.com/users/bugventure/gists{/gist_id}","starred_url":"https://api.github.com/users/bugventure/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/bugventure/subscriptions","organizations_url":"https://api.github.com/users/bugventure/orgs","repos_url":"https://api.github.com/users/bugventure/repos","events_url":"https://api.github.com/users/bugventure/events{/privacy}","received_events_url":"https://api.github.com/users/bugventure/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/epoberezkin/ajv/labels/enhancement","name":"enhancement","color":"84b6eb"}],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2015-06-15T10:10:58Z","updated_at":"2015-06-20T17:42:19Z","closed_at":"2015-06-20T17:42:19Z","body":"Hey, just wanted to say nice work on the performance improvements! It's great to see there's no upper limit in how fast a JSON validator for node can go. Caching the validator code internally is great and I guess does the trick for the benchmarks out there.\r\n\r\nI was wondering, do you plan on introducing some caching configuration? A limit on the size/number of cached validator code, maybe together with some policy for purging stale validators (e.g. least recently used)? That would help a great deal in large-scale projects with lots of schemas, or when schemas are dynamically generated and can change a lot.\r\n\r\nKeep up the good work!"}}