Today I was working on installing nodeunit for a test project I was creating, when I ran into an interesting error. This is a weird error. It would seem that NPM couldn’t find the folder under my $appdata%/Roaming folder… Therefore there must have been a problem when I first installed Node.js. The fix is simple. Go to the path and create the folder by hand. From there you should be completely in the clear! Give your npm command another try and enjoy!
Just got a Lenovo Yoga 2 Pro! Super Happy && Super Pumped! Wait one moment. There is something important you need to do!
You need to install and update your Intel drivers with the “Intel Driver Update Utility“.
Install it and enjoy :)!
If you haven’t been keeping up with my posts lately, then you are probably unaware of how I have been without a fully functioning laptop for the past couple of weeks. WELL! As of today I am no longer without a machine! Between my savings and a surprisingly random gift from my parents(Thank you so much!) I was able to get the Lenovo Yoga 2 Pro!
Now before you start bickering.. yes I know I just said the Lenovo Yoga 2 Pro.. that is because I wasn’t really interested in the 3 Pro… Yes, I am an outcast. Duly noted.
I won’t bother you with why I picked the laptop I got, because it is all based upon my opinion. Although I will mention.. I did get a very good deal… originally it was $1600 and I purchased mine for only around $1k. I am very pleased with my investment so far(Only had it for the day, dorks).
Without further adieu I shall present some photos:
Every website run’s into the ghost of a machine. Latency issues? Long responses for client requests? All ghosts, in which can make managing a DotNetNuke instance very painful. But what can we do?
Lets try and solve a couple of these problems!
As you can guess, the size of your database is very important. Lets clean it up a tad.
First take a look at your “EventLog” table. As you can probably guess from the name, it stores events that happen such as when a user log’s in, when someone tries to login, and just general errors that occur. Yes this is important, but honestly… it is only important in the beginning and the end of your applications life. During the middle of the applications life cycle, I suggest turning it off. Make sure you delete the irritating records left in the DB as well.
To Turn off the Event Log, go to your DNN Host Settings page, and ensure the “Site Log History” setting is set to 0(zero).
A couple other tables to clean out would be “SiteLog” and “Scheduler log”.. These records are also just wasting space on the disk.
As well, DNN has plenty of washed-up crappy scripts in it’s possession. You can fix a lot of this by using DNNScripts off of codeplex.
First thing to keeping a clean application, is when hosted with IIS. Make sure you application stays alive! If no one visits you website once every twenty minutes, IIS by default shuts it down, therefore causing the first user after those 20 minutes endure a painstakingly slow initial page load time. You can prevent this by using Pingdom or PingAlive . However, if you have access to the server, I suggest you change the Idle Time-out settings.
Afraid that the pinging will mess with your site statistics? Try creating a sub site, on the same application and then having the service ping it instead. That way you can go about your business as usual.
Here is another good resource on ensuring your application is alive at all times. I haven’t actually tried it though.. as it is not specific for DNN. : CodeProject – Keep Your Website Alive
Does you site have a lot of static information? Cache it! You can do this via changing the performance settings to heavy caching.
Make sure you use SQL Profiler to find long running scripts, usually from 3rd party modules. Then report those issues to their developers. I like to think, no script should surpass 500ms on the norm.
Remove unused modules from your server. If you aren’t using them, then neither should DNN. Get rid of them!
Install YSlow and make sure you get an A for performance! You can usually find errors in how things are GZIPed and maybe combine your CSS and JS files to get better performance.
Hopefully one or a few of these methods described will help you with your site. If you have any other tips or comments about how to improve DNN’s performance, feel free to let me know with a comment below.
My last post was written in frustration, along with the code I open sourced. I hope no one actually used it…
I am able to admit mistakes when I make them, and this was one. The problem lies in my understanding of all the paths I could of travelled to solve my problem. At the time I should of just taken a moment and sat back and relaxed, but instead I let my emotions and sleep deprived brain have the better of me. I believe if I had gotten a better grasp of the bigger picture, it would of helped me make a wiser decision.
P.S. I will be removing my last blog post, and perhaps the repository, soon.
I’ll end this post by releasing a small fraction of my frustration in a way, that one day might be used to help society:
“Too bad they don’t teach this kind of stuff along side my Computer Science courses at the University… because underwater basket weaving is so much more important to graduate…”
Goodnight world. Till next time.
Frustration has fallen upon me during development with Node.js and Socket.io. I’ve been working on a simple card game for the past month or two and keep running into an issue with the Socket.io library. That issue is the complexity of user/client management. Therefore I am currently working on a “Proof Of Concept” to help me work out the kinks for Socket.io and user management. If you’d like to join me or just view my progress feel free to check out the repository as follows.
P.S. Suggestions are welcomed.
INNER JOIN — Join columns, however remove records with null values.
LEFT/RIGHT JOIN — Join columns, and leave all columns there.
FULL JOIN — Join columns, even if there is only one match between tables.
It’s 2014 going on 2015 and yes, I know Windows 10 is near… However, this is the last time I am putting up with my unreliable Samsung Series 9. It seems every 6 to 8 months it decides to go corrupt and have me be forced to replace the SSD. NOT COOL! Don’t get me wrong… I loved it. I don’t hate Samsung. I just had a fluke. It was a model that they didn’t test property, and upon that it was basically rare hardware at the time. You could say I was the consumer beta test if you sole wanted.
Either way, I am beginning the investigation of a new laptop and plan on documenting the requirements for this laptop in this blog post. If you are a developer or just feel like I have missed something on this list, feel free to comment below letting me know! I am thinking about Lenovo and Asus, althought haven’t put my fist down on them yet.
Also just a note to everyone, the items are not in any particular order.
Last Updated: 10/15/2014 2:54pm
- 8+ GB of RAM
- 7+ hours of battery on a single charge.
- Must be able to virtualize.
- 256GB minimum SSD that works..
- 1080p screen, touch would be preferred.
- Would love a 2 in 1, but don’t mind it being just a laptop.
- Thin and light weight.
- No bigger than a 15.4 inch screen… minimum is 13.3(if even that…)
- Two 3.0 USB ports.
- Mini or full HDMI port.
- Bluetooth 4.0 L.E.
- Wireless b/g/n
- Strong body design… built for business.
Laptops that I am going to consider:
( Updated 11/18/2014 )
I plan on starting to assess the laptops in person tomorrow. Hopefully I can find some of them at my local stores.
Went to Best Buy the other day to see what the Yoga’s looked like and felt like. Seemed that they have pretty strong hinges for the convertibles, whereas they are made of a rubbery plastic. The screens were beautiful, yet they only had 13.3 inch models on display and in stock. I am feeling like the 13.3 inch is a bit small, and am feeling I would probably fit better with a 14 inch.
To vent a little bit about security, I come to you now. DO NOT send passwords in emails.
Emails are either plain text or HTML/CSS. Even with an encrypted path to the receiving person, it can still be tampered with. Also as a website owner you should never be able to look in your database and see anyone’s password anyways(hash that, salt that)… So why would you send it to them in an email, specifically when they register?
It is a fact that this is bad practice. Therefore any websites created as of 10/10/2014 and later.. heck like 10/10/2008 and later, I will not be using if such logic is overlooked.
Thank you for your time.