|
Three years ago when I needed to force my application to run on a 32 bit architecture I had to do a lot of work with memory usage. The big problem is a single case was over 1 GB and it needed to be entirely in memory for efficiency. After playing a lot of games with memory management (rebasing dlls, 3GB address space) I moved to 64 bit in 2009 and do not support 32 bit any more for these large cases. With 64 bit almost all memory problems disappeared. For my current application the data set is smaller (only 512MB) so 32 bit works fine. So I really do not worry about memory usage with this however it's not like I preallocate a several 100 MB buffers and do not use them.
John
|
|
|
|
|
ii_noname_ii wrote: Noone likes a "memory hog"... Sort by mem usage is the most used view in task manager
I would have thought sort by CPU usage was the most used. PCs these days have what, 2GB 4GB RAM? I would think that for typical users, "no one likes choppy apps due to CPU overuse" and "no one likes network stuttering" and "no one likes to see an app pause because the developer put blocking calls in the GUI thread" would typically take the cake over memory, but that's just my guess.
Then again, I am using 8.14GB of RAM at the moment with 129 tabs open in 9 chrome windows, 3 IDE instances, and various other apps. I have 16GB on my machine so I don't bother closing stuff I don't need at the moment, but on my 4GB laptop I rarely run into RAM use issues (network and CPU is more frequent). Of course, RAM constrained environments may be a different story (cell phones, virtual servers in the cloud for which one pays by RAM, etc.)
|
|
|
|
|
I am working on disconnected CAD/GIS (desktop) application where all the items are important and they are all difficult to achieve. Is it a sign of the time that these are not important to a lot of applications (e.g. the arch-typical 3 tier CRUD app)?
|
|
|
|
|
The list could go on:
- usability
- robustness
- understandable UI and so on
While I do agree that the choices given in the survey are often important for the overall solution I think the real value doesn't come from technical details.
|
|
|
|
|
That's true. I rated Responsiveness as the most critical, because for a client end application it is important for the user to be able to do their work efficiently. That is the whole point of software (most of the time). So if our application takes 5 mins to do something (and it sometimes does  ), then the customer will be unhappy and unable to do their work. But if it uses a bit more memory or CPU, it's not as bad. That being said, i do think that programmers should at least try to consider memory and CPU usage (and i do).
|
|
|
|
|
It looks to me that the survey was about the software in relation to the hardware. Usability and understandable UI are essentially the same thing and don't relate to hardware. Neither does robustness.
Responsiveness is the weakest of the group as it relates to hardware, but I might argue that responsiveness is a function of I/O which is hardware.
Just my opinion.
m.bergman
For Bruce Schneier, quanta only have one state : afraid.
To succeed in the world it is not enough to be stupid, you must also be well-mannered. -- Voltaire
|
|
|
|
|
The answers don't line up!
(4 and 5 options are lower than 1, 2 and 3 on Chrome 15)
Is it because there is no BACON?
Or because they should have used a CListCtrl?
[edit]Typo fixed: That -> than - OriginalGriff[/edit]
Ideological Purity is no substitute for being able to stick your thumb down a pipe to stop the water
|
|
|
|
|
OriginalGriff wrote: Is it because there is no BACON?
yes.
OriginalGriff wrote: Or because they should have used a CListCtrl?
yes...with added bacon.
Just along for the ride.
"the meat from that butcher is just the dogs danglies, absolutely amazing cuts of beef." - DaveAuld (2011)
"No, that is just the earthly manifestation of the Great God Retardon." - Nagy Vilmos (2011)
|
|
|
|
|
OriginalGriff wrote: The answers don't line up!
You'll notice "A clean looking form" was not one of the options in the list of considerations. 
Marc
|
|
|
|
|
Our software is deployed on thousands of seats in banks, the above criteria almost never come into discussions with clients, they care about security and functionality - as in many enterprise solutions our memory usage/cpu etc will never be an issue (unless we do something awful) compared so, say, stored procedure design, query optimisation etc etc.
|
|
|
|
|
I'm in a similar position and network and responsiveness as bloody relevant to us. Someone deploying an unresponsive app is an insult to all developers.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
Its a true fact is client don't care about anything that they can suggest...
as example :
if you put a button on the right side of the window instead left side(but it was suppose to be on left), client would think you a bid dumb, in most case they dont know what you do to develop an application.
Once I told my friend that computer works with only 0 and 1 nothing else he suggested me to stop study computer science 
|
|
|
|
|
This is by far the easiest poll I have seen. Where I work none of these items are of any real importance. Personally, I would like all of them to be important. But around here the most important item is one not included in the choices, "Just get it done and get it into production." Don't believe me, check my signature.
Comments from work:
- "Why can't you just do it like everybody else?"
- "Well, we haven't had any complaints yet."
- "I just want to get it into production."
I'm in space!
I know you are mate. Yep, we're both in space.
SPAAAACE!
|
|
|
|
|
Seconded.
We don't care with any of those as long as the "thing" does its job, and is reliable. Of course, the points listed are taken into account as metrics of efficency, but those are not the top priority.
|
|
|
|
|
Responsiveness - you mean this is not an important part of your design, do you pee in your boot as well.
Network is always an issue when a WAN is part of the equation.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
I do my best to not pee in my boots. It ruins the leather.  For me, almost all of these are important. And I would also include efficient, maintainable code, decent (prefer excellent) UI design with functionality that the user needs/wants. But that's just me. I'm generally in the minority when it comes to these types of discussions at work.
Comments from work:
- "Why can't you just do it like everybody else?"
- "Well, we haven't had any complaints yet."
- "I just want to get it into production."
I'm in space!
I know you are mate. Yep, we're both in space.
SPAAAACE!
|
|
|
|
|
I find memory, cpu and other hardware based issues to be minor issues. I'm quite happy for the junkyard people (IT) to throw more junk at the problem. The design issues I have strong views on and they get listened to as I set the rules.
One of the great things about age and experience, management tends to take you more seriously the more you have!
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
I hate when customer says "I don't care how it work, i only care results", and if it fails for memory issue then its my fault. The truth I learned is we can do it easily with computer because we studied it, we studied it because we have the capabilities. So when someone ask "Is this a easy job" I said "no its not, This will be done with the 4 years education and 3 years working experience. Its not an easy job to do".
|
|
|
|
|
... plus number of SQL queries and http requests (yes, I know they can be expressed in terms of CPU and network, but I found it very useful to treat them as a separate metric).
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
