[openstack-dev] [all][keystone] Increase of USER_ID length maximum from 64 to 255

Vishvananda Ishaya vishvananda at gmail.com
Mon Mar 3 19:09:33 UTC 2014


On Mar 3, 2014, at 6:48 AM, Jay Pipes <jaypipes at gmail.com> wrote:

> On Sun, 2014-03-02 at 12:05 -0800, Morgan Fainberg wrote:
>> Having done some work with MySQL (specifically around similar data
>> sets) and discussing the changes with some former coworkers (MySQL
>> experts) I am inclined to believe the move from varchar  to binary
>> absolutely would increase performance like this.
>> 
>> 
>> However, I would like to get some real benchmarks around it and if it
>> really makes a difference we should get a smart "UUID" type into the
>> common SQLlibs (can pgsql see a similar benefit? Db2?) I think this
>> conversation. Should be split off from the keystone one at hand - I
>> don't want valuable information / discussions to get lost.
> 
> No disagreement on either point. However, this should be done after the
> standardization to a UUID user_id in Keystone, as a separate performance
> improvement patch. Agree?
> 
> Best,
> -jay

-1

The expectation in other projects has been that project_ids and user_ids are opaque strings. I need to see more clear benefit to enforcing stricter typing on these, because I think it might break a lot of things.

Vish

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 455 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140303/87807dee/attachment.pgp>


More information about the OpenStack-dev mailing list