hiranya911
commented
4 years ago Did some rudimentary tests and all seems fine as far as I can tell. Tests were run on a laptop on my home wifi so the rpc latencies are a bit on the high side, but still looks quite reasonable.
Test 1
Following test calls verifyIdToken() 1000 times, and reports a performance summary.
@Test
public void testVerifyIdTokenPerformance() throws Exception {
String customToken = auth.createCustomToken("testuser");
final String idToken = signInWithCustomToken(customToken);
DescriptiveStatistics stats = new DescriptiveStatistics();
for (int i = 0; i < 1000; i++) {
long time = timeIt(new Callable<FirebaseToken>() {
@Override
public FirebaseToken call() throws Exception {
return auth.verifyIdToken(idToken);
}
});
stats.addValue(time);
}
System.out.println("Min: " + stats.getMin());
System.out.println("Max: " + stats.getMax());
System.out.println("Average: " + stats.getMean());
System.out.println("99p: " + stats.getPercentile(99));
}
private long timeIt(Callable<?> callable) {
long start = System.nanoTime();
try {
callable.call();
} catch (Exception e) {
throw new RuntimeException(e);
}
return TimeUnit.NANOSECONDS.toMillis(System.nanoTime() - start);
}And the results I get look quite good (all values are in milliseconds):
Min: 0.0
Max: 72.0
Average: 0.2569999999999967
99p: 3.0The max value of 72ms is from the very first call to verifyIdToken(). This is the slowest since it needs to fetch public keys and cache them. All subsequent calls completed under 12ms, as they don't require any RPC calls.
Test 2
Following test calls getUser() 35 times and simply reports the time each call took:
@Test
public void testGetUserPerformance() {
for (int i = 0; i < 35; i++) {
long time = timeIt(new Callable<UserRecord>() {
@Override
public UserRecord call() throws Exception {
return auth.getUser("testuser");
}
});
System.out.println(time);
}
}And the times reported are:
1111 242 224 236 222 779 277
205 207 239 241 213 214 191
205 243 229 264 212 195 227
211 220 229 215 218 221 221
270 197 212 209 207 226 214Again the first call is the slowest (TCP handshake, SSL handshake, OAuth2 credentials fetch etc). But most of the subsequent calls completed under 250ms, except for one which took 779ms. That seems acceptable for a test conducted over wifi.
deepfriedbrain
Operating System version: MacOS 10.15.5 Firebase SDK version: 6.12.2 Library version: 6.12.2 Firebase Product: auth
I've migrated from Google Identity Toolkit to Firebase Auth. I'm using this library on my server, which is hosted on Google App Engine (Java).
I've observed that very often, a simple call
auth.verifyIdTokenhas been taking 3-5 seconds (yes 3000-5000ms)!Usually it would take less than 10ms, but very frequently, it would take 3-5 seconds to complete. It's happening way too frequently to ignore especially in the past few hours.
auth.getUserconsistently takes even longer. The minimum that this API takes is about 700ms, which itself is a lot for the best case scenario.Are you guys aware of this problem? I have the logs with timestamps captured. I can provide specific details you need.