My after hours project

to be honest I haven't yet. i have perf reporting enabled and will deal with perf issues when they arise. i don't want to prematurely optimize anything

heh. Optimizing entityframework is not premature, that thing is slow as hell (startup).
 
to be fair ef6 and even 5 were faster than previous versions but yeah it can be a bit sluggish i guess.

what do you suggest? firing off some queries on start up?

Not trying to be funny here, but sluggish is not the word i'd use to describe and im not comparing previous versions. We have just finished a small internal platform with it, this rubbish thing takes like 35 seconds to spool up and this is EF6 im using.

Firing off queries will not help remember that the global asax is fired for users on page load, so you will just be back at square one.


You can try this -> http://msdn.microsoft.com/en-us/data/dn582034
 
dude that's just weird. i haven't experienced anything like what you're describing in devscore or anywhere else tbh.

and nothing i have found online regarding perf and ef6 seems to be similar either.

im not going to start precompiling because of data access. if it ever gets to that point ill switch it for something else.

right now my biggest perf issue is the client side. everything server side is under 20ms. client side that big ass image is my biggest worry..

and that's a cold start.

dude something must be wrong on your system. 30 seconds for anything is not right.
 
dude that's just weird. i haven't experienced anything like what you're describing in devscore or anywhere else tbh.

and nothing i have found online regarding perf and ef6 seems to be similar either.

im not going to start precompiling because of data access. if it ever gets to that point ill switch it for something else.

right now my biggest perf issue is the client side. everything server side is under 20ms. client side that big ass image is my biggest worry..

and that's a cold start.

dude something must be wrong on your system. 30 seconds for anything is not right.

There is nothing wrong with the system, its only EF that is slow. Everything else loads and executes within 10ms. We are in the process right now of actually getting rid of EF. And i highly doubt you've looked properly there are numerous if not hundreds of complaints about EF speed.
 
dude, i looked by going to google and typing in "ef6 slow", "ef6 speed issue", "ef6 sluggish start". is that not looking properly? i don't really know what to say. im sorry you're having 30 second weird issues. but i can't find any other people online having 30 second issues. maybe my google-fu just sucks.
 
dude, i looked by going to google and typing in "ef6 slow", "ef6 speed issue", "ef6 sluggish start". is that not looking properly? i don't really know what to say. im sorry you're having 30 second weird issues. but i can't find any other people online having 30 second issues. maybe my google-fu just sucks.

Okay.

I never said everyone else has 30 second cold starts, i just said mine is. But there are people that struggle with the speed maybe not as severe as mine.

http://www.infoq.com/news/2013/11/ef-6-performance-issues
http://stackoverflow.com/questions/...r-slow-during-the-1st-query-but-only-in-debug
https://entityframework.codeplex.com/workitem/1781

And those were the first few links. So yes perhaps your google-fu does suck.
 
dude. i don't even know what we're doing here. im not defending ef's perf at all and im not trying to prove you wrong.
all of those posts i saw and read and all of them pertain to the same issue you linked to at codeplex that was closed in december and fixed and rolled out. the issue has been continued in https://entityframework.codeplex.com/workitem/1829 as well which was closed in feb.

most of those issues are either db first, or really large, really complicated objects. with tons of rows. my whole db right now is like 8 megs. i have 11 tables. the most rows i have in a table is 300. lazy loading also seems to complicate things a bit regarding EF's perf and im not using lazy loading.

im not saying don't throw out EF if it doesn't work for you, im saying im not worried about EF's perf right now in my project. its not that big, its not that complex and its not a threat right now at this point in time. :D

to be honest i have only used EF in like 3 live work projects, one of which is relatively busy. its adequate, not great. and it definitely wouldn't be my first choice for a really intensive app. when you pull EF what are you going to replace it with?
 
to be honest i have only used EF in like 3 live work projects, one of which is relatively busy. its adequate, not great. and it definitely wouldn't be my first choice for a really intensive app. when you pull EF what are you going to replace it with?

We've changed our layer into a tooling framework to do code first (it just wasnt ready at the time).

Our one table has a few million records in it, and we have some insanely complex join queries with rank partitions.
 
made a thread on reddit and another forum im on. getting plenty of views but not a lot of reviews. any idea how to get people to enter their details in? im trying to lower the barrier to entry and streamline as much as possible but just can't seem to get people to review their companies...
 
spent like an hour and a half last night messing around trying to get that silly drop down on the home page to be "on top" of the section break.

i really should learn more about css because i honestly don't even know where to start troubleshooting when it comes to css. i open firebug, go to the css tab or examine the element and just type random **** in
 
Top
Sign up to the MyBroadband newsletter
X