Hi,
So it turned out that the slowness of Ipsilon was caused by the lack of keys on the database, so it got slower over time, as more entries got added.
I just ran the following queries to create new indexes on production, could I get any +1s retroactive?
----------------------------------------------------- ALTER TABLE association ADD PRIMARY KEY (uuid,name); CREATE INDEX ON association (uuid);
ALTER TABLE dbinfo ADD PRIMARY KEY (name, option); CREATE INDEX ON dbinfo (name);
ALTER TABLE openid_data ADD PRIMARY KEY (name, option); CREATE INDEX ON openid_data (name);
ALTER TABLE sessions ADD PRIMARY KEY (id); CREATE INDEX ON sessions (expiration_time);
ALTER TABLE transactions ADD PRIMARY KEY (uuid, name); CREATE INDEX ON transactions (uuid);
ALTER TABLE users ADD PRIMARY KEY (name, option); CREATE INDEX ON users (name); -----------------------------------------------------
With kind regards, Patrick Uiterwijk Fedora Infra
On Tue, Aug 11, 2015 at 06:54:58AM -0400, Patrick Uiterwijk wrote:
Hi,
So it turned out that the slowness of Ipsilon was caused by the lack of keys on the database, so it got slower over time, as more entries got added.
I just ran the following queries to create new indexes on production, could I get any +1s retroactive?
ALTER TABLE association ADD PRIMARY KEY (uuid,name); CREATE INDEX ON association (uuid);
ALTER TABLE dbinfo ADD PRIMARY KEY (name, option); CREATE INDEX ON dbinfo (name);
ALTER TABLE openid_data ADD PRIMARY KEY (name, option); CREATE INDEX ON openid_data (name);
ALTER TABLE sessions ADD PRIMARY KEY (id); CREATE INDEX ON sessions (expiration_time);
ALTER TABLE transactions ADD PRIMARY KEY (uuid, name); CREATE INDEX ON transactions (uuid);
ALTER TABLE users ADD PRIMARY KEY (name, option); CREATE INDEX ON users (name);
Def +1 :)
Pierre
infrastructure@lists.fedoraproject.org