Lightbulb???;)
They are all simpler than those new crazy ATX powerbuttons... the ones that don't show which state they are in... and you have to hold them in to shut them off...
What we need are red levers. One side says "ON"
the other says "NOT ON".
and then a note that says "Do not leave lever in middle position."
I figure if people can remember to start a car, they can figure out how to turn on a machine.
But then again... I may be oversimplifying things...
I couldn't agree more.
It happens in more areas than startups with VCs.
All companies wanting to go from small to big hit the same thing. If the reason they are growing is because the market demand is higher than they can keep up with, the all-mighty dollar is the only real way through the problem.
I have seen and read about this at several places.
It costs a ton of money to catch up with the big boys.
A 64x64 pixel block for a movie, unless the renderer has some amazing pre-processing, would require some majore bandwidth of propriatary data. No major studio will allow such a possibility. All 3-d data is considered intellectual property. Also, lets say you are rendering a little bitty block of Godzilla sqaushing a building. A bit of the foot, a bit of the building. Mostlikely all of the 3-d data for the foot and the building will need to be sent over. Also, the texture files need to be sent, and those textures, even if only some scale patches can be in the hundreds of megabytes.
I don't see it happeneing. The money being spent for the little return is not worth it. It would be cheaper to spend the $200-500k on a render farm that you keep or even leasing systems for less.
As I have said many times, true render farms need loads of memory.
I wouldn't want a render box with less than 1 gig of ram. Regardless of what renderer you are using, if you really need a render farm, you are going to have to spend money on MHZ and memory.
I wish it could be different.
They aren't proprietary like the 320's were. From tests I have ran, the 550 was better than the Octane and almost as fast as the Octane 2.
It is expensive for an Intel box, and you could probably build one for 2/3 the price... but SGI support is still SGI support, and to many buisness that means something.
I like the fact that hardware is catching up to some of the rendering algorithms and ideas that are used in software rendering.
The better the hardware can simulate what a rendered image will look like, untill it is good enough to produce fullmotion 3D video on the fly, the less test renders will be needed. That makes my life sooo much easier. It almost bugs me how much of my cpu time is used for throw away images...
if only you could sell frames on ebay...;)
if you want something that has a sharp UI and runs on Linux, wait a few months for Maya to come out.
Between hot-boxes and hot keys, the menu is never needed and most commands are a small mouse move away.
Sure it will cost a bundle, but CG is one of the places where quality does not come cheap.
i know that Maya has a hardware render option, where it renders the image in hardware. Well... actually it displays the frame through OpenGL and then saves it as an image to disk.
I imagine others have this too... it just isn't used for professional quality.
What I am supprised to see is the lack of mention in the article to NVidia and SGI. The new SGI Intel boxes are running a variation of the nv15 chipset (and do a good job of it). Also, NVidia, if I remember right, has a ton of ex-SGI employees.
Yes but the difference is that OpenGL is just that... and open standard. If SGI got all upset about it, then they would no longer have an open standard.
Part of SGI owning the highend GL market for such a long time was that they had a spec that they created and extended and hardware that rocked on it. By keeping it open, others could learn it and program for it, always wishing for that day that they had an SGI box to *really* play with it on.
Closing the standard would have been worse for SGI then had IBM squashed all the IBM compatables.
Re:Be Aware of the powerdrain !!!
on
Cheap Linux PDAs
·
· Score: 3
I see... so your *developer* eddition didn't work out for you. You mean that it looks like some work could be done on it?
I too have been a little frustrated with mine, but I understand that the system isn't final. People are still working on it, writing apps for it, tweaking the kernel for it.
Is it a finsished product, no. But if you read the developers information, it will not be a big supprise or dissapointment.
Now my Open Source ignorance is going to shine through. I am a huge advocate but I have to admit that I get lost in what I see as grey areas.
GPL questions...
I understand that copying and pasting somebody's code into your code is a bad thing. What about using a Perl module (you are including source with your source code). Or libraries that are GPLed but your code is not?
I could be missing the boat here. If I am not modifying the work that they have done and I am not including what they did with my software but it requires it to operate, is that wrong.
I can think of scripts I wrote in school that used Perl modules to get stuff done. Should those scripts be opened up?
Although this may be a fake, it is possible.
My friends and I have done it.
We built a basic varriant of a spud gun with a 4 ft PVC barrel that was just big enough to hold cans.
So we tried it. And did it ever work.
We blew bark off of trees, we lost several cans as well. We had no way to guage how fast it was going, but we were launching it with ~80 psi from a pressure tank that was over twice the diamater but only 2 feet long.
We would fire at about a 75 degree angle and the can would go over 100 yards. It was a fun time.
I dissagree.
I don't think that the 12:1 ratio is correct, but it could be an exageration on your part...
I can see this as being important where machines are not at 100% useage most of the time and where redundancy is a must. Like the average web farm.
With this you could afford to put a few more boxes in place and survive abnormaly large traffic just as well with smart web routing packages. A much better performance than what you would get on a single box.
I see a few problems with your comments.
1)Your issue with lack of support.
They provide a servide. They support that service. Try calling Ford about the diesel engine you dropped in your brand new Tarus. I am positive it will no longer be covered in a bumper to bumper waranty.
Just because you want them to provide or support a service does not mean that they do or should have to.
2)The attitude that the help desk should spend his time learning from your call. He has other customers, those staying inside the box that are on hold. He should help them first. Had you called at 4:30 am, it might have been different. Also, if a company thinks it is worth the tech guys time to learn about an alternate way of using them, they would send him to a class.
3)Thee fact that they get paid tons of money.
I imagine that the person is not rolling in the dough as you suggest. If this was a first level tech guy, I am almost positive. Not to knock the job, cause I value good support people, but I don't see it as one of the more desirable jobs, which brings me to my last problem.
4)The negative attitude that they had against you.
I have a feeling from your post, that you may not have handled the situation well, I know you aren't now, it is very negative and bitter. This attitude shows on the phone more than people know.
To summarize, I think you need to take a deep breath, realize that they had a job which they did. Maybe they didn't respond all rosey about the whole thing, but they could of had a long day. Now that you know how to do what you want, do something about it. Put together a reffernce page to tell others how to do what you did, maybe even a HOW-TO. After it is done, and done well, send it along to the support email address for the service provider. Maybe they will add support when they see how easy it is, you never know.
Keep a positive attitude with them, it will help in the long run.
Because the when you make your own wheel, you can custome build it to protect yourself.
Imagine if Apple released all of its open-source stuff under GPL and we found that some prorietary Apple binary that was later downloaded used some of this GPL'ed code. Apple would have to open all of that code. If Apple makes its own license, I am more than positive that it would give its self a way out.
It is just good buisness sense.
Slashdot Mirror
Larry the Cucumber and Bob the Tomato...
and zidgel, fidgel, midgel and kevin as well...
And the job isn't that bad, either...
Lightbulb??? ;)
They are all simpler than those new crazy ATX powerbuttons... the ones that don't show which state they are in... and you have to hold them in to shut them off...
What we need are red levers. One side says "ON"
the other says "NOT ON".
and then a note that says "Do not leave lever in middle position."
I figure if people can remember to start a car, they can figure out how to turn on a machine.
But then again... I may be oversimplifying things...
I couldn't agree more.
It happens in more areas than startups with VCs.
All companies wanting to go from small to big hit the same thing. If the reason they are growing is because the market demand is higher than they can keep up with, the all-mighty dollar is the only real way through the problem.
I have seen and read about this at several places.
It costs a ton of money to catch up with the big boys.
i always thought that was 1/0 (one slash zero) not I/O (eye slash oh).
It made sense... true is on false is off...
but I am a geek...
A 64x64 pixel block for a movie, unless the renderer has some amazing pre-processing, would require some majore bandwidth of propriatary data. No major studio will allow such a possibility. All 3-d data is considered intellectual property. Also, lets say you are rendering a little bitty block of Godzilla sqaushing a building. A bit of the foot, a bit of the building. Mostlikely all of the 3-d data for the foot and the building will need to be sent over. Also, the texture files need to be sent, and those textures, even if only some scale patches can be in the hundreds of megabytes.
I don't see it happeneing. The money being spent for the little return is not worth it. It would be cheaper to spend the $200-500k on a render farm that you keep or even leasing systems for less.
After running Maya for Linux, my dual 500 celeron (366 oc'ed ;) ) was not enough. Now a 1ghz system...
and waiting for the geforce 3 to cheaper....
so, the software to "force" upgrades is just in the highend area.
As I have said many times, true render farms need loads of memory.
I wouldn't want a render box with less than 1 gig of ram. Regardless of what renderer you are using, if you really need a render farm, you are going to have to spend money on MHZ and memory.
I wish it could be different.
Umm... have you played on the SGI 550's?
They aren't proprietary like the 320's were. From tests I have ran, the 550 was better than the Octane and almost as fast as the Octane 2.
It is expensive for an Intel box, and you could probably build one for 2/3 the price... but SGI support is still SGI support, and to many buisness that means something.
Blue who?
;)
I have been breathing perl for to long of time...
maybe I should look at this python beast...
Can a python play nice with veggies and penguins?
I think the idea is more programinf *for* the PDA, not on it. Cross compiling will allow you to do all development outside of testing off of the PDA.
Wrong. We have 4.6+ running on IRIX.
I like the fact that hardware is catching up to some of the rendering algorithms and ideas that are used in software rendering.
;)
The better the hardware can simulate what a rendered image will look like, untill it is good enough to produce fullmotion 3D video on the fly, the less test renders will be needed. That makes my life sooo much easier. It almost bugs me how much of my cpu time is used for throw away images...
if only you could sell frames on ebay...
Does this mean that you are questioning authority???
By questioning him, are you acknowledging his authority?
if you want something that has a sharp UI and runs on Linux, wait a few months for Maya to come out.
Between hot-boxes and hot keys, the menu is never needed and most commands are a small mouse move away.
Sure it will cost a bundle, but CG is one of the places where quality does not come cheap.
i know that Maya has a hardware render option, where it renders the image in hardware. Well... actually it displays the frame through OpenGL and then saves it as an image to disk.
I imagine others have this too... it just isn't used for professional quality.
What I am supprised to see is the lack of mention in the article to NVidia and SGI. The new SGI Intel boxes are running a variation of the nv15 chipset (and do a good job of it). Also, NVidia, if I remember right, has a ton of ex-SGI employees.
Yes but the difference is that OpenGL is just that... and open standard. If SGI got all upset about it, then they would no longer have an open standard.
Part of SGI owning the highend GL market for such a long time was that they had a spec that they created and extended and hardware that rocked on it. By keeping it open, others could learn it and program for it, always wishing for that day that they had an SGI box to *really* play with it on.
Closing the standard would have been worse for SGI then had IBM squashed all the IBM compatables.
I see... so your *developer* eddition didn't work out for you. You mean that it looks like some work could be done on it?
I too have been a little frustrated with mine, but I understand that the system isn't final. People are still working on it, writing apps for it, tweaking the kernel for it.
Is it a finsished product, no. But if you read the developers information, it will not be a big supprise or dissapointment.
My list goes as follows: ;)
Fisher
Manson (famous psychos)
Partridge (famous families)
Pear (things found in a pear tree)
Orange (fruit)
Purple (color)
Flash (jumpin jack flash - whoopi goldberg movies)
Bicycle (Queen songs)
Scooter (transportation)
Oscar (mupets)
Marlin (fish)
Seminoles (Florida teams)
Apache (Indian tribes)
and finally IIS (web servers)
Maybe some of these are streaches.
Everybody knows that only the 31337 H4X0RZ (or 'leet haxors) call it LIN-U-UX. It only the script kiddies would ever think something different.
Now my Open Source ignorance is going to shine through. I am a huge advocate but I have to admit that I get lost in what I see as grey areas.
GPL questions...
I understand that copying and pasting somebody's code into your code is a bad thing. What about using a Perl module (you are including source with your source code). Or libraries that are GPLed but your code is not?
I could be missing the boat here. If I am not modifying the work that they have done and I am not including what they did with my software but it requires it to operate, is that wrong.
I can think of scripts I wrote in school that used Perl modules to get stuff done. Should those scripts be opened up?
How far does it reach?
Although this may be a fake, it is possible.
My friends and I have done it.
We built a basic varriant of a spud gun with a 4 ft PVC barrel that was just big enough to hold cans.
So we tried it. And did it ever work.
We blew bark off of trees, we lost several cans as well. We had no way to guage how fast it was going, but we were launching it with ~80 psi from a pressure tank that was over twice the diamater but only 2 feet long.
We would fire at about a 75 degree angle and the can would go over 100 yards. It was a fun time.
Ah, the fun you can have in the country.
I dissagree.
I don't think that the 12:1 ratio is correct, but it could be an exageration on your part...
I can see this as being important where machines are not at 100% useage most of the time and where redundancy is a must. Like the average web farm.
With this you could afford to put a few more boxes in place and survive abnormaly large traffic just as well with smart web routing packages. A much better performance than what you would get on a single box.
I see a few problems with your comments.
1)Your issue with lack of support.
They provide a servide. They support that service. Try calling Ford about the diesel engine you dropped in your brand new Tarus. I am positive it will no longer be covered in a bumper to bumper waranty.
Just because you want them to provide or support a service does not mean that they do or should have to.
2)The attitude that the help desk should spend his time learning from your call. He has other customers, those staying inside the box that are on hold. He should help them first. Had you called at 4:30 am, it might have been different. Also, if a company thinks it is worth the tech guys time to learn about an alternate way of using them, they would send him to a class.
3)Thee fact that they get paid tons of money.
I imagine that the person is not rolling in the dough as you suggest. If this was a first level tech guy, I am almost positive. Not to knock the job, cause I value good support people, but I don't see it as one of the more desirable jobs, which brings me to my last problem.
4)The negative attitude that they had against you.
I have a feeling from your post, that you may not have handled the situation well, I know you aren't now, it is very negative and bitter. This attitude shows on the phone more than people know.
To summarize, I think you need to take a deep breath, realize that they had a job which they did. Maybe they didn't respond all rosey about the whole thing, but they could of had a long day. Now that you know how to do what you want, do something about it. Put together a reffernce page to tell others how to do what you did, maybe even a HOW-TO. After it is done, and done well, send it along to the support email address for the service provider. Maybe they will add support when they see how easy it is, you never know.
Keep a positive attitude with them, it will help in the long run.
Because the when you make your own wheel, you can custome build it to protect yourself.
Imagine if Apple released all of its open-source stuff under GPL and we found that some prorietary Apple binary that was later downloaded used some of this GPL'ed code. Apple would have to open all of that code. If Apple makes its own license, I am more than positive that it would give its self a way out.
It is just good buisness sense.