VCIO-next: The vulnerability details view UI is too slow to render

[tdruez]

From aboutcode-org/dejacode#220 (comment)

@DennisClark I noticed that when I click on a Vulnerability VCID it takes at least 20 seconds to open that vulnerability in public2. I opened public and pasted a VCID there and it also seems really sluggish. I suppose it might have something to do with the high number of affected packages. Do you know if there are performance improvements that still need to be deployed on our public and public2 servers? I am concerned that the really slow response could be rather annoying to a DejaCode user, even though it is a VCIO problem. (Maybe a message such as "Getting affected packages list ..." would take care of it.) Please suggest what we ought to do, if anything, about this, thanks.

A URL such as https://public.vulnerablecode.io/vulnerabilities/VCID-hh72-ne73-aaak can take up to 60 seconds (and sometime timeout) making the app unusable.

[pombredanne]

Here is what I suggest:

1. We need to tune Postgres conf. Right now the public DB servers uses less than 2GB out of 64GB

2. The UI should be simplified after some profiling. In particular we should:
   2.1. Remove all package details and open packages in a new page, only on request
   2.2. Move Severities to a new tab
   2.3. Keep weaknesses in a Essentials tab
   2.4. Remove Severities score ranges