Mohit's profileTime Ticking...PhotosBlogListsMore Tools Help

Blog


    October 15

    Green Computing for Processors!!!!

    Just came across an article in Digit's october issue (with good focus on laptops - as i m in search for one & a really gud cover photo )

    It says tht "Physics guarantees that a computer will not be able to "discard" more than 3.5 X (10^22) bits of physical information per second"!! For each computation - like an addition - it adds two numbers into one which esstentially means that bits for two numbers that were added are dissipated as heat. As because of physical limits, there is an upper bound of heat dissipation, so processor wont be able to discard more bits than a certain level!!

    Based on current fastest processors, scientists say we are around 1,00,000 times slower than the max limit. And this will be covered somewhere in around 20-30 yrs, which implies saturation after that period. The issues of heat dissipation because of high electron movement and leakage will start arising more we move towards that limit. Moreover, power required for those speeds would be enormous which may just add to the existing issues of generating more and more power and seriously considering some renewable sources of energy.

    Thus, scientists are working on something to "reuse the bits" and "stop throwing them away". Uncompute the unneeded bits. This is what they call as Reversible Computing. And yes, this is what they call as GREEN COMPUTING !!!

    Well, a brief idea that is being worked upon to realize this concept is via the use of Ballistic Circuits/Adiabatic Circuits, which means circuit with less or without flow of heat. Here, bits are not lost because they dont dissipate into heat. Because of less flow of heat in circuits, the bits are not thrown away and can be used in another computation as well.

    This will allow faster processors, more shrinked chips, cost-effective systems and prevent environmental degradation issues.

    Well, must say, it would be a big challenge for scientists to put things into effect but certainly would mean beginning of a new generation of processors !!!
    September 08

    Limitation of SSIS Buffers

    SSIS provides a configurable setting of Data Flow Task, DefaultMaxBufferSize which defines the size of SSIS buffer. It also has a non-configurable property named MaxBufferSize which is set to 100 MB and can not be changed.
    While creating data flow custom components (source / destination), our team allowed components to handle data more than the available limit. For example, the Oracle Bulk Load Destination component, which allows bulk loading of data into Oracle Server, can take more than 100 MB data and load it into Oracle Sever. Also, source components, such as Oracle Source component, allow users to set properties and fetch more number of rows. But because of 100 MB limit, SSIS throws "Memory Out of Range Exception" while our server systems has huge amount of RAM available.
    Well, it would be certainly better if SSIS allow using more buffer. In any case, if system will run out even of virtual memory, it will throw a system exception but making a pre-assumption and setting limits such as 100 MB limits the performance of SSIS.