Gabriel Moreira created TINKERPOP-1189:
------------------------------------------
Summary: SimpleAuthenticator over HttpChannelizer makes Gremlin
Server pretty slow and consumes more CPU
Key: TINKERPOP-1189
URL: https://issues.apache.org/jira/browse/TINKERPOP-1189
Project: TinkerPop
Issue Type: Improvement
Components: server
Affects Versions: 3.0.2-incubating
Environment: Gremlin Server 3.0.2 backended by Titan 1.0.0 and
Cassandra (separate instance), running in a server with 2 CPUs / 7.5 GB RAM
(Linux Debian 3.16.7)
Reporter: Gabriel Moreira
Priority: Minor
I have setup Authorization in my Gremlin Server instances (v3.0.2), backended
by Titan v1.0.0 and Cassandra.
I am testing SimpleAuthenticator, with the following snippet from my
gremlin-server.yaml:
authentication: {
className: org.apache.tinkerpop.gremlin.server.auth.SimpleAuthenticator,
config: {
credentialsDb: conf/tinkergraph-empty.properties,
credentialsDbLocation: data/credentials.kryo}}
ssl: {
enabled: false}
I am using the default serialization file of TinkerGraph credentials.kryo, with
only the default user stephen/password.
I am using Basic Auth in my requests to Gremlin Server, by passing the header
"Authorization" with the value "Basic c3RlcGhlbjpwYXNzd29yZA==".
Authorization works as expected. Therefore, the Gremlin Server becomes pretty
slow! It takes 10x more time and consumes 5x more CPU (from 10% to 50%) to
handle the same simple traversal Http POST request (below) in batch, compared
to Gremlin Server with NO authorization!
{
"gremlin": "g.V().has('CONTENT','id', 'LinkPost:7330001').count()"
}
Is there a workaround to this?
Ps. If there is a fix, could it be patched for version 3.0.2? I am limited to
this version because I use Titan 1.0.0.
Thanks.
Gabriel Moreira
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
