chore: Collection note update on get_or_create behaviour

- Added note for performance impacts of SSL termination in Chroma.

docs/core/collections.md

@@ -80,6 +80,7 @@ col = client.get_or_create_collection("test", metadata={"key": "value"})
 !!! warn "Metadata with `get_or_create_collection()`"
 
     If the collection exists and metadata is provided in the method it will attempt to overwrite the existing metadata.
+    This behaviour may be fixed by this [GH issue](https://github.com/chroma-core/chroma/issues/2390)
 
 ### Deleting a collection
 

docs/security/chroma-ssl-cert.md

@@ -6,6 +6,12 @@ Chroma uses uvicorn as an ASGI server, which can be configured to use SSL/TLS ce
 
     Using certificates with Chroma CLI is not yet supported.
 
+??? tip "Performance Impact"
+
+    Using certificates within Chroma will have a performance impact as `uvicorn` will need to hnadle 
+    the encryption and decryption of the data. If performance is of concern, 
+    consider using a reverse proxy like `nginx` or `envoy` to handle the SSL/TLS termination.
+
 ## Self-Signed Certificates
 
 ### Creating a self-signed certificate