Jump to content

tricecold

Members
  • Content count

    131
  • Donations

    0.00 CAD 
  • Joined

  • Last visited

  • Days Won

    2

tricecold last won the day on July 25 2015

tricecold had the most liked content!

Community Reputation

18 Good

About tricecold

  • Rank
    Initiate

Contact Methods

  • Website URL
    http://www.timucinozger.com

Personal Information

  • Name
    Tim
  • Location
    Montreal

Recent Profile Visitors

3,832 profile views
  1. Is AMD potentially risky? (Threadripper)

    Yes but htop looks much nşcer with HT on
  2. Is AMD potentially risky? (Threadripper)

    No 8700 for general use
  3. Is AMD potentially risky? (Threadripper)

    I think i7 8700 is a better option than ryzen now, that's what I have been advicing people
  4. Is AMD potentially risky? (Threadripper)

    64 with logicals
  5. Is AMD potentially risky? (Threadripper)

    My point is instead of buying a 7960 and complete the rest of the system and end up spending 3K , I would definitely build two 1950Xs one with cheap components and one as main machine possibly for 3K if not a little more, which in the end I would end up having 64 3+ GHz cores( drooling) But this becomes a heavy simulation lifter in the end, for rendering I would spend that money only on GPUs so it's always up to the user
  6. Is AMD potentially risky? (Threadripper)

    I am not saying TR is the fastest processor because it's not, but for sub 1K range IMHO it is the logical choice. As for the second PC part, it doesn't need high speed disks or SSDs since rendering a frame or a big simulation caching will definitely going to take more than a few minutes per frame, a slow disk will suffice.
  7. Is AMD potentially risky? (Threadripper)

    Not necessarily, u can make a second TR with much cheaper components, can use it for distributed simulations etc or renders. Second box doesn't need a fancy video card or a case monitor or other additional costs. Also I always find it very strange to do a comparison for a couple that costs 900 to another one that costs 2000. If the performance difference is not %200 better , there is a clear winner for me
  8. Is AMD potentially risky? (Threadripper)

    You can buy 2X 1950X with the price of one i9 7960, 7960 is not even the competitor because it costs more than double the prize of a 1950
  9. Is AMD potentially risky? (Threadripper)

    you can always tell a software to use n amount of cores, just leave at least one or two free
  10. Is AMD potentially risky? (Threadripper)

    Honestly, I couldn't been happier with my TR choice. It was obviously a huge leap from 2600K which is a glorified file server and render manager now. But with my TR I can render and do comp at the same time whooaaat. It's not the fastest CPU out there but for it's price range it's the damn best IMHO. For an fx td
  11. Is AMD potentially risky? (Threadripper)

    Mine worked straight out of box on Ubuntu 17.04, well kubuntu tbh, with CPU flag, so I ak guessing this is OS related
  12. Is AMD potentially risky? (Threadripper)

    no no, i tried it inside Houdini with the environment flag on and off and with opencl ticket on and off, its almost twice as fast with the flag on, without the flag on in houdini.env and openCL ticket , its more than twice the speed, i will run the command once i get back also
  13. Is AMD potentially risky? (Threadripper)

    Hey, so it works here, I am on Ubuntu 16.04 cliinfo ICD loader properties ICD loader Name OpenCL ICD Loader ICD loader Vendor OCL Icd free software ICD loader Version 2.2.8 ICD loader Profile OpenCL 1.2 Device Name GeForce GTX 970 Device Vendor NVIDIA Corporation Device Vendor ID 0x10de Device Version OpenCL 1.2 CUDA Driver Version 375.66 Device OpenCL C Version OpenCL C 1.2
  14. Is AMD potentially risky? (Threadripper)

    Will try in an hour and let you know
  15. Is AMD potentially risky? (Threadripper)

    It's Abit confusing, the thing is by default openCL tick box will use your GPU not CPU, if you want OpenCL to be ran on CPU , there was a flag you need to put in your houdini.env which I don't remember
×