Soma Posted February 6, 2014 Share Posted February 6, 2014 When on projects with lots of fields (+100), the loading of the setup fields list takes 4-5 seconds. What I think could be cool is if they load via ajax. Not sure about details but I use tags often then to group them. Maybe after certain amount of fields and tags, collapse the sections and only load the fields in them when openened. Just something to think about. Link to comment Share on other sites More sharing options...
renobird Posted February 6, 2014 Share Posted February 6, 2014 Soma, I have an install with 100+ fields (seems insane, but this install handles several custom web apps). I haven't really noticed setup > fields loading THAT slow, but it does lag a bit. It's been less of an issue with the "quicklinks" to fields in the new admin themes — which even with 100+ still works great. I like the idea of of collapsing the fields after a certain number and loading via ajax, especially if it saved the state of the list. Good call. Link to comment Share on other sites More sharing options...
Martijn Geerts Posted February 6, 2014 Share Posted February 6, 2014 Install here 100 fields. no noticeable slowdown. Link to comment Share on other sites More sharing options...
Soma Posted February 6, 2014 Author Share Posted February 6, 2014 146 here and growing still, and very noticable slowdown. Other admin pages and Server is fast. Link to comment Share on other sites More sharing options...
ryan Posted February 8, 2014 Share Posted February 8, 2014 I'm not getting any perceptible slowdown with 100+ fields here. Soma do you have any modules hooking into the rendering on that screen? Considering how quickly the dropdown navigation versions can be generated, I'm guessing the slowdown may have something to do with the calculation of # templates and # pages that are shown. If I can get a copy of your database dump, I could import here and test. It's been less of an issue with the "quicklinks" to fields in the new admin themes — which even with 100+ still works great. These were actually just converted to AJAX yesterday, so that they don't have to be loaded/rendered on every admin page request. This also removes the 100 field/template limitation that we'd imposed on it. 1 Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now