Skip to content

Conversation

@LukasReschke
Copy link
Member

This will result in only one decryption and encryption call per request resulting in a better performance. Now the overhead is about 2ms for the encryption which is negligible. Especially since I found another bottleneck that stealing us 20ms 50ms that I have fixed in #18914 🙊

Ref #18482 (comment)

cc @karlitschek @icewind1991

@karlitschek
Copy link
Contributor

sweeeet 👍

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could we also batch writes? maybe write in the destructor?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Implemented

@LukasReschke LukasReschke force-pushed the put-in-single-field-for-speed branch from ddbc277 to fd5c360 Compare September 8, 2015 20:08
@LukasReschke
Copy link
Member Author

  • After installation user is not logged-in anymore automatically

@LukasReschke LukasReschke force-pushed the put-in-single-field-for-speed branch from fd5c360 to b085071 Compare September 8, 2015 21:19
@LukasReschke LukasReschke force-pushed the put-in-single-field-for-speed branch from b085071 to 0b91087 Compare September 9, 2015 10:48
@scrutinizer-notifier
Copy link

A new inspection was created.

@LukasReschke
Copy link
Member Author

@icewind1991 @MorrisJobke Mind a review? THX.

@LukasReschke
Copy link
Member Author

2015-09-09_12-50-53

@icewind1991
Copy link
Contributor

👍 looks good

@karlitschek
Copy link
Contributor

better 👍

LukasReschke added a commit that referenced this pull request Sep 9, 2015
Put session data in single field for speed
@LukasReschke LukasReschke merged commit a05ccd9 into master Sep 9, 2015
@LukasReschke LukasReschke deleted the put-in-single-field-for-speed branch September 9, 2015 12:10
@MorrisJobke MorrisJobke added this to the 8.2-current milestone Sep 9, 2015
@PVince81
Copy link
Contributor

Regression: #19273

@LukasReschke
Copy link
Member Author

Nope. Not me to blame. 🙊 🙈 🙉

@PVince81
Copy link
Contributor

I didn't git blame you, only git bisected 😉

@LukasReschke
Copy link
Member Author

Hahaha 😄 😆

@lock lock bot locked as resolved and limited conversation to collaborators Aug 10, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants