A fully-searchable and accessible archive of court data including growing repositories of opinions, oral arguments, judges, judicial financial records, and federal filings.
We finally have a baseline of what our performance looks like on average. It's not horrible, but I think there's room for improvement. The hard part is figuring out what's wrong, but now we can measure each step we take and see what it does.
If this is the correct definition of types:
o | Case law opinions
r | List of Federal cases (dockets) with up to three nested documents.
rd | Federal filing documents from PACER
d | Federal cases (dockets) from PACER
p | Judges
oa | Oral argument audio files
here are some results:
A few ideas:
More CPU via more nodes
More disk speed via AWS tweak
What else?
I think this can wait until our new dev ops person comes on and it should be a good one for them. Eventually I'd also like to get this info into Grafana somehow, so we can see a chart of these speeds, but, well, all in due time!
We finally have a baseline of what our performance looks like on average. It's not horrible, but I think there's room for improvement. The hard part is figuring out what's wrong, but now we can measure each step we take and see what it does.
A few ideas:
What else?
I think this can wait until our new dev ops person comes on and it should be a good one for them. Eventually I'd also like to get this info into Grafana somehow, so we can see a chart of these speeds, but, well, all in due time!
Originally posted by @legaltextai in #4209