• Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.
  • Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!

SKA news

Collapse
X
  •  
  • Filter
  • Time
  • Show
Clear All
new posts

    Originally posted by AtW View Post
    Not if you get requests from 1/4 million unique IPs over TCP/IP.

    Is it just me who thinks minestrone is an idiot?
    I think you opened up a SKA thread, told us twitter worked only half the time, reduced to 10% when pressed, argued 10% was a half.

    Comment


      Originally posted by AtW View Post
      I think you'll run out of TCP/IP sockets.
      You only need one on the server side. Do you mean file descriptors?
      While you're waiting, read the free novel we sent you. It's a Spanish story about a guy named 'Manual.'

      Comment


        Originally posted by minestrone View Post
        I think you opened up a SKA thread, told us twitter worked only half the time, reduced to 10% when pressed, argued 10% was a half.
        You can't trust AtW just because he sometimes sounds like he knows about technical issues. After all, as the saying goes, even a stopped clock is right half the time.
        Originally posted by MaryPoppins
        I'd still not breastfeed a nazi
        Originally posted by vetran
        Urine is quite nourishing

        Comment


          Originally posted by doodab View Post
          You only need one on the server side. Do you mean file descriptors?
          I just had a chat with our network admin and you right, there can be more than 64k internal sockets provided there is enough memory to handle it, however I still maintain 1 mln calls per 1 sec would have more overheads than handling one call sending 140 MB.

          Comment


            Originally posted by AtW View Post
            It does not say database here, text field can be in memcache or on disk.

            If you keep 140 MB file in a database then you are an idiot.
            Pick out where I said MBs Alexi?

            140 chars was my only data description you will find.

            Completely unable to understand basic quantities you are.

            Comment


              1 table with one text field of 140 chars if that gets accessed 1 million times in 1 second
              Originally posted by AtW View Post
              It does not say database here, text field can be in memcache or on disk.
              It just seemed like he meant a database table to me. Maybe he didn't. We should ask him.

              Originally posted by AtW View Post
              If you keep 140 MB file in a database then you are an idiot.
              That depends. A lot of document management systems do just that. In my last gig I had to move ~15TB of files (10s of millions, some quite large) out of a database to a file system and provide multiple access paths to them. We gained a lot in ease of access but lost out in terms of being able to search the metadata, as FS metadata isn't really optimised for that.
              While you're waiting, read the free novel we sent you. It's a Spanish story about a guy named 'Manual.'

              Comment


                Originally posted by minestrone View Post
                Pick out where I said MBs Alexi? 140 chars was my only data description you will find. Completely unable to understand basic quantities you are.
                Well, char for me in C# is 2 bytes, and in other times including database is 1 byte, if I wanted 2 bytes in DB then I'd expect some other term wchar (?).

                Anyhow, I need to get back and do monthly invoices. Go look at something shiny ministrone.

                Comment


                  Originally posted by doodab View Post
                  It just seemed like he meant a database table to me. Maybe he didn't. We should ask him.
                  Well, let's assume he meant database, in this case I'd keep such data structures in memory and it won't be an issue to query them - there won't be a big delay reading 140 MB.

                  Comment


                    Originally posted by AtW View Post
                    I just had a chat with our network admin and you right, there can be more than 64k internal sockets provided there is enough memory to handle it, however I still maintain 1 mln calls per 1 sec would have more overheads than handling one call sending 140 MB.
                    Yes I agree. But it was you who said that

                    Originally posted by you
                    Front end stuff is very easy to run in parallel very cheaply
                    I was just pointing out that it's doable.
                    While you're waiting, read the free novel we sent you. It's a Spanish story about a guy named 'Manual.'

                    Comment


                      Originally posted by AtW View Post
                      I need to get back and do monthly invoices. Go look at something shiny ministrone.
                      I will and I can because I have something shiny to look at with lots of shiny things. I own a house, you do not.

                      You are a Russian financial immigrant who split a job when you got a passport and lived off the tax payer for years.

                      I have said before you have cost this country more than you can give.

                      Sue me.

                      Comment

                      Working...
                      X